Skip to content
This repository was archived by the owner on Feb 9, 2024. It is now read-only.

Commit c30de6f

Browse files
authored
Update README.md link to moved content (#89)
Previous link was archived and moved to: https://kotlinlang.org/docs/native-concurrency.html#object-transfer-and-freezing
1 parent 680f1ae commit c30de6f

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ In the sample directory, there is a sample project that demonstrates adding Coro
101101

102102
## CoroutineWorker Prefers Frozen State
103103

104-
Object detachment (i.e. [transferring object ownership](https://github.com/JetBrains/kotlin-native/blob/master/CONCURRENCY.md#object-transfer-and-freezing) from one thread to another) is relatively difficult to achieve (outside of simple scenarios) compared to working with objects that are frozen and immutable. Because of this, CoroutineWorker prefers taking the frozen, immutable route:
104+
Object detachment (i.e. [transferring object ownership](https://kotlinlang.org/docs/native-concurrency.html#object-transfer-and-freezing) from one thread to another) is relatively difficult to achieve (outside of simple scenarios) compared to working with objects that are frozen and immutable. Because of this, CoroutineWorker prefers taking the frozen, immutable route:
105105

106106
- Lambdas passed to CoroutineWorker are automatically frozen when they are going to be passed across threads.
107107
- The result value from `withContext` is also frozen.

0 commit comments

Comments
 (0)