so who here is working on a Kotlin (Native) based ...

# kotlin-native

[badlogic]

so who here is working on a Kotlin (Native) based cross-platform game framework engine? let me know, so I don’t have to.

[sksk]

badlogic: omg native libGDX yes pls best framework that ever existed

[olonho]

@badlogic: Mario, it would be truly amazing if it was you 🙂

[badlogic]

welp, let’s wait for threading to arrive in kotlin native 🙂

[olonho]

I'm working on threading with following restriction: object subgraphs can be transferred between threads, so that either one or another thread can access it, but not two simultaneously. Would it be sufficient for your needs?

[spierce7]

What is an object subgraph? How could you ensure that only 1 thread has access to the object at any given time? That seems difficult to restrict.

[olonho]

I will follow up with more details, once have viable implementation

[cbruegg]

Sounds like an error-prone approach to threading TBH.

[badlogic]

@olonho I guess one could work with this, however, a single code base for Kotlin Native and Kotlin JVM would be harder to maintain that way. What are the issues with a shared memory model? ref counting not being thread safe?

[olonho]

because it raises all the standard issues with MT programming which I find one of the major computer science failures 😉. We believe that coroutines for blocking IO and workers for computation offload is saner approach to concurrency problem in general Take a look on API I sketched in https://github.com/JetBrains/kotlin-native/pull/655/files - would it be sufficient for GDX needs?

[spierce7]

Do workers have a 1 to 1 relationship with threads?

[olonho]

Implementation-wise, there will be a thread bound to the worker, but it is possible to create a thread, and run Kotlin code there, but it doesn't have to be worker, and process its job queue, so I'd say it's an immersion, not isomorphism