one more questions:sweat_smile: <https://kotlinlan...
# ktor
h
one more questions😅 https://kotlinlang.slack.com/archives/C1CFAFJSK/p1597886480055300 ktor client 1.4.0 seems related to coroutines-core:1.3.9-native-mt when I use all of the below, there is error shared on the link • maven-publish • coroutine 1.3.9 • ktor-client-core 1.4.0 is there some workaround not to use native-mt? or instead, is it fine to use ktor 1.3.2 with kotlin 1.4.0?
l
I'd say no to both.
h
Thanks for replying🙏, then, will it be better to use kotlin 1.4 after native-mt is stable?
l
@elizarov Might have a better answer than me.
🙏 1
e
We are looking at how we can best integrate
native-mt
into the general release process for
kotlinx.coroutines
, so that you don't have to go through all those hoops.
l
Am I right to think that native-mt features will be included by default only when the new Kotlin/Native Memory Management is released?
e
No. There is no need to wait. The current code in native-mt branch seems to be good enough as a short-term solution. People successfully use it in their apps. Indeed, it is hard to maintain, but that's Ok, since we don't plan to live with it forever. So far, we see that whatever problems people report we are able to fix.
l
So it might be default soon?
e
Yes. That's the plan.
👍 5
🎉 7
h
That sounds good. currently, I experience two issues and felt mt is too early stage. but as it’ll be default soon. I’ll report my problem on youtrack, and keep using it. Thanks all. 🙏
l
@Hyun kotlinx.coroutines issues are tracked on GitHub, unlike ktor FYI.
h
@louiscad Thanks for your kindness 🙂
I reported two problem. wish all is resolved.😄 native-mt with MutableStateFlow ktor with native-mt
👍 1