:mega: :mega: :mega: kotlinx.coroutines 1.6.0-RC i...
# coroutines
v
๐Ÿ“ฃ ๐Ÿ“ฃ ๐Ÿ“ฃ kotlinx.coroutines 1.6.0-RC is here! Major highligths: โ€ข Completely reworked and now multiplatform kotlinx-coroutines-test module. โ€ข New API to manage dispatchers:
limitedParallelism
along with
<http://Dispatchers.IO|Dispatchers.IO>
being unbound for limited parallelism views. โ€ข K/N new memory model is now part of the release and all the coroutine primitives can be shared across multiple threads if the new memory model is enabled. โ€ข A lot of improvements and bug fixes. Full changelog: https://github.com/Kotlin/kotlinx.coroutines/releases/tag/1.6.0-RC
K 26
โค๏ธ 8
๐ŸŽ‰ 31
๐Ÿ”ฅ 12
๐Ÿ™Œ๐Ÿผ 2
๐Ÿ™Œ 8
j
Awesome, I was looking forward to seeing the
kotlinx-coroutines-test
lib become multiplatform. THANK YOU ๐Ÿ™
โž• 4
b
+1 to that. I can finally remove my hacky workarounds in jsMain(s) ๐Ÿ˜„
j
message has been deleted
๐Ÿ‘ 1
macOS, iOS and so on are missing
@Vsevolod Tolstopyatov [JB] are they being deployed or there was an issue?
j
@Vsevolod Tolstopyatov [JB] his point was about
kotlinx-coroutines-test
, not
kotlinx-coroutines-core
๐Ÿ‘ 1
And indeed I don't see iOS stuff either:
v
Oh, thanks for pointing it out! It seems to be either build or sonatype issue, Iโ€™m investigating it right now
๐Ÿ™ 2
๐Ÿ‘€ 1
t
Will there be a native-mt for 1.6.0-RC?
b
No, release notes state that -native-mt is no longer needed and main artefacts will pick up new memory model if enabled.
t
But the new memory model isn't production ready yet
From the release notes if you are opted in it will use, which is great, but if you aren't opted in I assumed it defaults to the old single threaded implementation
b
Oh you mean frozen mt. Yeah, might be worth sticking with -native-mt until new mm stabilises. No idea then.
j
@Vsevolod Tolstopyatov [JB] still missing apple artifacts ๐Ÿ˜ž
@Vsevolod Tolstopyatov [JB]] I know I am disturbing, but is there any ETA about this one? maybe 1.6.0 final?
v
Iโ€™ve located the problem and the proper artifcats will either be released along with 1.6.0 final or 1.6.0-RC2
l
What was the problem exactly?
j
milestones are on github?
j
Do you have any ETA for the 1.6.0-RC2 or 1.6.0 release with iOS artifacts?
๐Ÿ‘€ 1