Use ConcurrentHashMap
for JVM target
#39
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#38 attempts to use AndroidX Collection KMP on JVM and iOS (and a few others) for the thread-safe mutable map implementation to address JVM performance issue with Stately.
However both our basic
JvmConcurrencyTest
and lincheck surfacedConcurrentModificationException
in AndroidX Collection'sSimpleArrayMap
.This PR instead use
ConcurrentHashMap
for JVM, and Stately for all other targets.Our
JvmConturrencyTest
is passing but Lincheck's Model checking test still surfaces some linearizability issues with ourRealCache
implementation, though it's not a regression. #47