The other option is to have an unfrozen object ins...
# touchlab-tools
k
The other option is to have an unfrozen object instance in “limbo”, from a memory perspective. Then have it attach to whatever thread you’re accessing it from, then when you’re done, detach. Other callers would block waiting for it. This is one of those things that sounds nice but will be a nightmare in practice. We don’t do any unfrozen state transfer in our code. You rarely need to do it, and there are a number of potential issues: https://dev.to/touchlab/kotlin-native-transferring-state-4n8i