mega mega mega kotlinx coroutines 1 3 6 release `StateFlow`

Question

mega mega mega 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 · Answer

are there any docs on how to integrate with BlockHound

streetsofboston · Answer

Wow the `StateFlow` api addition was speeeeedy slightly smiling face

v0ldem0rt · Answer

Oh no I missed the train for <https github com Kotlin kotlinx coroutines issues 2003> disappointed

Vsevolod Tolstopyatov [JB] · Answer

< Dariusz Kuc> our integration is automatically discovered by BlockHound it s enough to enable it

Dariusz Kuc · Answer

Awesome

Marcelo Hernandez · Answer

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] · Answer

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 · Answer

Looks like an issue has already been filed for this <https github com Kotlin kotlinx coroutines issues 2004>

rkeazor · Answer

Awesome work JB Team < elizarov>

ursus · Answer

Is StateFlow rx BehaviorRelay

gabin · Answer

< ursus> no it s more like LiveData

streetsofboston · Answer

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

myanmarking · Answer

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 · Answer

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 · Answer

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 · Answer

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 · Answer

I think your looking for this <https github com Kotlin kotlinx coroutines issues 1261>

rkeazor · Answer

< myanmarking>

myanmarking · Answer

yes thank you i was aware Unfortunatly still coming stuck out tongue

rkeazor · Answer

No prob dude

ursus · Answer

so refCount replay etc is still not there

elizarov · Answer

They ll come a bit later

Brendan Weinstein · Answer

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 · Answer

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 >