hi all, does someone knows why this happens and how can it be fixed? kotlin.native.concurrent.InvalidMutabilityException: mutation attempt of frozen kotlin.collections.HashMap@2fbf0c8 at kfun:kotlin.Throwable.<init>(kotlin.String?;kotlin.Throwable?)kotlin.Throwable (00000000007e0e00) at ThrowInvalidMutabilityException (00000000004c8d50) at kfun:kotlin.collections.HashMap.<set-length>#internal (00000000007ea080) at kfun:kotlin.collections.HashMap.addKey$stdlib(K)kotlin.Int (00000000007eaea0) at kfun:kotlin.collections.HashMap.put(K;V)V? (00000000007ec770) at kfun:com.senaptec.toolframework.util.FontLoader.$loadCOROUTINE$108.invokeSuspend(kotlin.Result<kotlin.Any?>)kotlin.Any? (0000000000560d10)

Is this on Mac target ?

mac and mingw

Most likely, yes. Objects and all other top-level constructs are frozen on creation, as are all its properties. Even though its a MutableMap, that map is still frozen and can’t be edited

s*it

Nope, companion objects are still considered top-level. Super annoying, I know. You will have to use one of the atomics from the Stately lib to do any modification on singletons https://github.com/touchlab/Stately

🤦‍♂️

Yeah I know, it drives me crazy. The alternative is to make it a local object and use DI to it where you need it. Korge has an injector module which could probably make this a bit less painful

uhmm, good idea

what about korge 2 with its new kotlin mp version?

I haven’t tried 2.0 yet. But it’s not a limititation of korge, it’s a fundamental restriction from Kotlin Native. No way around it other than using atomics or not using global objects

ok, will go with DI, in fact i like the idea of using DI in the project from an architecture point of view

This video tutorial touches briefly on it, but I’m not aware of any other docs

thx man, watching now