:mega: :mega: :mega: `kotlinx.coroutines` 1.3.0-RC...

# coroutines

[Vsevolod Tolstopyatov [JB]]

📣 📣 📣 kotlinx.coroutines 1.3.0-RC2 is here!

Changelog:
* New flow operator families
* combine and combineTransform
* flatMapLatest, mapLatest, transformLatest and collectLatest
* R8-friendly ServiceLoader 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

[Adam Powell]

I'm enjoying transformLatest so far 👍

[sdeleuze]

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

[sdeleuze]

@Vsevolod Tolstopyatov [JB] Is there some replacements for FlowAsPublisherKt.from and PublisherAsFlowKt.from that I was calling from Java previously?

[Vsevolod Tolstopyatov [JB]]

Only `asFlow`/`asPublisher` extensions in kotlinx.coroutines.reactive.FlowKt

[sdeleuze]

So I have to call it from Kotlin now ?

[sdeleuze]

It's doable just want to be sure

[Vsevolod Tolstopyatov [JB]]

You still can call an extension method from Java, e.g.: asPublisher(flow)

[sdeleuze]

Oh I had a conflict with import kotlinx.coroutines.flow.FlowKt

[sdeleuze]

asFlux is not accessible from Java ?

[Vsevolod Tolstopyatov [JB]]

asFlux is also accessible, but it’s in the reactor module and sub-package.

[sdeleuze]

Ok

[Vsevolod Tolstopyatov [JB]]

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

[sdeleuze]

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

[sdeleuze]

I am more puzzled by breakages in my integration tests

[sdeleuze]

I will send you the detail via direct messages

[sdeleuze]

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