mega mega mega `kotlinx coroutines` 1 3 0 RC2 is here Chang kotlinlang #coroutines

usage to enable SL optimization on Android toolchain 3.6.0+ * Stacktrace recovery for minified Android builds * Full-blown interop between coroutine context and Reactor context * Various fixes and improvements * Full changelog: https://github.com/Kotlin/kotlinx.coroutines/releases/tag/1.3.0-rc2

👏 22

👍 3

🐿 2

👀 3

🍻 1

🎉 5

😒uspend: 3

Adam Powell

08/09/2019, 8:43 PM

I'm enjoying

transformLatest

so far 👍

sdeleuze

08/09/2019, 8:50 PM

Thanks for the great work on Reactor interop I will test it next week

@Vsevolod Tolstopyatov [JB] Is there some replacements for

FlowAsPublisherKt.from

and

PublisherAsFlowKt.from

that I was calling from Java previously?

Vsevolod Tolstopyatov [JB]

08/14/2019, 8:32 AM

Only `asFlow`/`asPublisher` extensions in

kotlinx.coroutines.reactive.FlowKt

sdeleuze

08/14/2019, 8:32 AM

So I have to call it from Kotlin now ?

It's doable just want to be sure

Vsevolod Tolstopyatov [JB]

08/14/2019, 8:34 AM

You still can call an extension method from Java, e.g.:

asPublisher(flow)

sdeleuze

08/14/2019, 8:36 AM

Oh I had a conflict with import

kotlinx.coroutines.flow.FlowKt

asFlux

is not accessible from Java ?

Vsevolod Tolstopyatov [JB]

08/14/2019, 8:38 AM

asFlux

is also accessible, but it’s in the

reactor

module and sub-package.

sdeleuze

08/14/2019, 8:39 AM

Vsevolod Tolstopyatov [JB]

08/14/2019, 8:50 AM

Do you feel like this part of the integration can be somehow improved in terms of user experience?

sdeleuze

08/14/2019, 9:04 AM

I think I can live with that that's not a very common use case and in any case that will be at framework level

I am more puzzled by breakages in my integration tests

I will send you the detail via direct messages

I found the cause of the issue (the conversion was not active due to classpath detection I had to update to follow your changes)

4 Views

#coroutines Join Slack