:mega: :mega: :mega: kotlinx.coroutines 1.3.6 release: - `StateFlow` for reactive state handling i...

# coroutines

[Vsevolod Tolstopyatov [JB]]

📣 📣 📣 kotlinx.coroutines 1.3.6 release:

• StateFlow for reactive state handling is here!
• Most of the existing Flow operators have left their experimental status
• runInterruptible primitive for tying cancellation and interruptions
• Integration module for RxJava3
• Integration with BlockHound to detect inappropriate blocking calls
Thanks to all contributors!
Full changelog: https://github.com/Kotlin/kotlinx.coroutines/releases/tag/1.3.6

[Dariusz Kuc]

are there any docs on how to integrate with BlockHound?

[streetsofboston]

Wow… the StateFlow api addition was speeeeedy! 🙂

[v0ldem0rt]

Oh no I missed the train for https://github.com/Kotlin/kotlinx.coroutines/issues/2003 😞

[Vsevolod Tolstopyatov [JB]]

@Dariusz Kuc our integration is automatically discovered by BlockHound, it’s enough to enable it (https://github.com/reactor/BlockHound/blob/master/docs/quick_start.md)

[Dariusz Kuc]

Awesome!!!

[Marcelo Hernandez]

Awesome! I just put up a PR to upgrade our Android project to this. We run lint against our project and seems that with this update, we are running into the following lint error:

Error: Invalid package reference in org.jetbrains.kotlinx:kotlinx-coroutines-core; not included in Android: java.lang.instrument. Referenced from kotlinx.coroutines.debug.AgentPremain. [InvalidPackage]

Any thoughts?

[Vsevolod Tolstopyatov [JB]]

You can safely disable this warning in your config, meanwhile I will think about a way to fix it without changing everyone’s lint config

[Marcelo Hernandez]

Looks like an issue has already been filed for this. https://github.com/Kotlin/kotlinx.coroutines/issues/2004

[rkeazor]

Awesome work JB Team @elizarov

[ursus]

Is StateFlow rx BehaviorRelay?

[gabin]

@ursus no, it’s more like LiveData

[streetsofboston]

MutableStateFlows are like BehaviorSubjects in Rx, but MutableStateFlow must have an initial value.

[myanmarking]

can any1 please clarify this: 'if you put events into the StateFlow, protect them from double-processing with flags'. I dont understand its meaning

[rkeazor]

It probably means ,so the events don't get re-triggered when the flow gets collected from agian . Thats what I thought it ment when I read it in the documentation last night. but don't quote me on in it. might be completely wrong lol

[myanmarking]

oh yes that was my instinct as well. To be honest, this StateFlow was not what i was expecting, at least until it's complete. The only few use cases that is missing from Flow is the ability to share a single collector, for instance, observe something and every time that flow is collected, just compute the chain once. Something like a 'share' operator. I was expecting StateFlow to cover that, and it doesn't for now. I don't see any benefit over ConflatedBroadCastChannel for now. May be wrong

[myanmarking]

This:

val stateFlow = flow { Random.nextInt() }.shareIn(thisScope)

Assert.assertEquals(
    stateFlow.first(),
    stateFlow.first()
)

For me, the only thing missing in flow api. Other use cases i can cover with custom operators

[rkeazor]

I think your looking for this https://github.com/Kotlin/kotlinx.coroutines/issues/1261

[rkeazor]

@myanmarking

[myanmarking]

yes, thank you i was aware. Unfortunatly, still coming 😛

[rkeazor]

No prob dude

[ursus]

so refCount, replay, etc is still not there?

[elizarov]

They’ll come a bit later.

[Brendan Weinstein]

I might be looking in the wrong place; I am not seeing the new version in maven

https://mvnrepository.com/artifact/org.jetbrains.kotlinx/kotlinx-coroutines-core

Hopefully there will be a new native-mt release; there's at least one bug fix I am eagerly awaiting.

[octylFractal]

I think mvnrepository is just indexing a bit slow, they're certainly in central: https://repo1.maven.org/maven2/org/jetbrains/kotlinx/kotlinx-coroutines-core/1.3.6/