You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2021. It is now read-only.
It would be great if it were clarified in https://github.com/JetBrains/kotlin-native/blob/master/CONCURRENCY.md that any time an object is referenced by two functions that can change the coroutine context (eg async, launch, withContext, suspending function) that the object will be frozen. It'd be helpful to drive home the point by showing an example where the coroutine is executed on a single thread but objects are still frozen.
This probably belongs as documentation in the coroutines library for native mt coroutines when it's released, since this is behavior controlled by that library
It would be great if it were clarified in https://github.com/JetBrains/kotlin-native/blob/master/CONCURRENCY.md that any time an object is referenced by two functions that can change the coroutine context (eg async, launch, withContext, suspending function) that the object will be frozen. It'd be helpful to drive home the point by showing an example where the coroutine is executed on a single thread but objects are still frozen.
This came up as a problem here ktorio/ktor#1537
The text was updated successfully, but these errors were encountered: