Have project use the new memory model

[twyatt]

https://blog.jetbrains.com/kotlin/2021/08/try-the-new-kotlin-native-memory-manager-development-preview/

Evaluate if:

• any atomics can be replaces with raw types
• usages of Stately can be replaced by Tuulbox's SynchronizedMap
  • Stately spins up a thread on JVM target for handling isolated operations, we're also not disposing of these when done with them

To do:

• Update project readme gradle instructions Had already been updated via Add Gradle configuration instructions for "new memory model" #313

[volo-droid]

There's a new version of Stately available 2.0.0 (so far there's a release candidate 2.0.0-rc2), which uses the new memory model, deprecates stately-iso-collections, and suggests to use stately-concurrent-collections instead.

It would be cool if Kable migrates to that version (or alternatively removes Stately all together) otherwise it's impossible to use Stately concurrent collections together with Kable in one project because of a linking error for iOS/Mac targets:

e: Module "co.touchlab:stately-isolate" has a reference to symbol co.touchlab.stately.concurrency/GuardedStableRef|null[0]. Neither the module itself nor its dependencies contain such declaration.

[twyatt]

Thanks for the info, I had planned to remove Stately entirely but I was unaware of stately-concurrent-collections. That looks like a good choice. Super helpful that you pointed that out!
It is high up on my to do list to get these changes in.

[twyatt]

@volo-droid I published a SNAPSHOT version for testing (from #437) that has Stately removed:

repositories {
    maven("https://oss.sonatype.org/content/repositories/snapshots")
}

dependencies {
    implementation("com.juul.kable:core:0.21.0-issue-237-1-SNAPSHOT")
}

[volo-droid]

Thanks @twyatt . The project can be built with that version, Mac version crashes on consuming scanner.advertisements but I have to figure out if the issue is on our side or caused by the library.