Hi guys is TrieMap.getOrElseUpdate a thread-safe method ? As is not mentioned in Java docs
The docs about
TrieMap say it is a concurrent thread-safe lock-free implementation. That should mean that all methods are thread-safe.
It seems in
2.11.6 they have solved the atomiciy problem and its not yet thread-safe
It sounds like you’ve seen https://github.com/scala/bug/issues/7943
Yes for sure i traced the PR to see if they have reached to solution and made it thread-safe in the
2.11.6 milesone ?
Yes, that’s right, it seems to have been fixed since 2015. At least, there haven’t been any reports to the contrary that I know of.