Hey guys! I have an implementation doubt, may be you can help me: I have a shared single common class that internally holds a

MutableMap

, so: For JVM: I use the

ConcurrentHashMap

class For Web: I use just a

mutableMapOf

But for Native, I have to

freeze()

the singleton to avoid the

IncorrectDereferenceException

. So, if the whole graph is frozen, I don’t know how to have a

MutableMap

inside it. Any tips?

Hey, checkout https://github.com/touchlab/Stately

If you can wait for 1.3.70, there’s a new stately thing. Thread-isolated mutability! Way faster than the original stately collections. https://github.com/touchlab/Stately/blob/kpg/iso_state/stately-iso-collections/src/commonMain/kotlin/co/touchlab/stately/collections/IsoMutableMap.kt

Thanks! I’ll take at look at that library. For now, I’ve drafted this class, and seems to work well (except for entries, keys and values collections), but I’m not using it

Yeah, no JS for

stately-collections

There was a reason but I don’t recall offhand

Browsers are single threaded maybe? The thing is that without it I can’t use this library, at least not without a simple dependency on commonMain 😞

Testing issues according to this comment https://github.com/touchlab/Stately/blame/05758c76b43ac7eb58027d60efe043f75c50273e/stately-collections/build.gradle#L82

Had nothing to do with single threaded. I haven’t looked at it much in recent times because it’s always been on the list of things that was going to get a refactor.