azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update kotlin-native/NEW_MM.md

Browse Source
This commit is contained in:
Svyatoslav Scherbina
2021-08-31 08:30:09 +00:00
committed by Space
parent 712f7daeb2
commit 64dc19fafb
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
kotlin-native/NEW_MM.md
+14 -1
View File
@@ -36,7 +36,7 @@ Together with the new MM we are bringing in another set of changes:
### Update the Kotlin/Native compiler ### Update the Kotlin/Native compiler
Update to Kotlin/Native 1.6.0-dev (**TODO**: specify the exact version) and enable dev repositories (**TODO**: Remove after we update to M1): Update to Kotlin/Native 1.6.0-M1-124 and enable dev repositories:
```kotlin ```kotlin
// build.gradle.kts // build.gradle.kts
@@ -77,13 +77,26 @@ kotlin.targets.withType(KotlinNativeTarget::class.java) {
To fully take advantage of the new MM, newer versions of libraries were released: To fully take advantage of the new MM, newer versions of libraries were released:
* `kotlinx.coroutines`: `1.5.1-new-mm-dev2` at https://maven.pkg.jetbrains.space/public/p/kotlinx-coroutines/maven * `kotlinx.coroutines`: `1.5.1-new-mm-dev2` at https://maven.pkg.jetbrains.space/public/p/kotlinx-coroutines/maven
* No freezing, every common primitive (Channels, Flows, coroutines) work through worker boundaries. * No freezing, every common primitive (Channels, Flows, coroutines) work through worker boundaries.
* Unlike `native-mt` version, library objects are transparent for `freeze`: if you freeze e.g. a channel, all of its internals will get frozen,
and it won't work as expected. In particular, this can happen when freezing something that captures a channel.
* `Dispatchers.Default` is backed by a pool of workers on Linux and Windows, and by a global queue on Apple targets. * `Dispatchers.Default` is backed by a pool of workers on Linux and Windows, and by a global queue on Apple targets.
* `newSingleThreadContext` to create coroutine dispatcher backed by a worker. * `newSingleThreadContext` to create coroutine dispatcher backed by a worker.
* `newFixedThreadPoolContext` to create coroutine dispatcher backed by a pool of `N` workers. * `newFixedThreadPoolContext` to create coroutine dispatcher backed by a pool of `N` workers.
* `Dispatchers.Main` backed by main queue on Darwin and by standalone worker on other platforms. **NOTE**: _Don't use `Dispatchers.Main` in unit-tests, because nothing is processing the main thread queue in unit-tests._ * `Dispatchers.Main` backed by main queue on Darwin and by standalone worker on other platforms. **NOTE**: _Don't use `Dispatchers.Main` in unit-tests, because nothing is processing the main thread queue in unit-tests._
* `ktor`: `1.6.2-native-mm-eap-196` at https://maven.pkg.jetbrains.space/public/p/ktor/eap * `ktor`: `1.6.2-native-mm-eap-196` at https://maven.pkg.jetbrains.space/public/p/ktor/eap
### Using previous versions of the libraries
You can continue using previous versions of the libraries in your project.
Older versions (including `native-mt` for `kotlinx.coroutines`) could still be used, and the existing code will work just like with the previous MM. Older versions (including `native-mt` for `kotlinx.coroutines`) could still be used, and the existing code will work just like with the previous MM.
The only known exception is creating Ktor HTTP client with default engine using `HttpClient()`. You will get
```
kotlin.IllegalStateException: Failed to find HttpClientEngineContainer. Consider adding [HttpClientEngine] implementation in dependencies.
```
To fix this, specify the engine explicitly, by replacing `HttpClient()` with `HttpClient(Ios)` or other supported engine
(see [the documentation](https://ktor.io/docs/http-client-engines.html#native) for more details).
Other libraries might also have compatibility issues. If you encounter any, please report to the library authors.
## Performance issues ## Performance issues