https://kotlinlang.org logo
#coroutines
Title
# coroutines
x

xenomachina

03/05/2021, 11:45 PM
Are there any plans for
ReceiveChannel.isClosedForReceive
to graduate from being "experimental"?
The reason I ask is that we were using some
@ExperimentalTime
stuff, and the upgrade from kotlinx-coroutines-core-jvm-1.4.2 to kotlinx-coroutines-core-jvm-1.4.3 caused this code to blow up, non-deterministically, at runtime. So now we're removing all uses of
@ExperimentalTime
and also
@ExperimentalCoroutinesApi
because they just seem too risky. There isn't a great alternative to
isClosedForReceive
in some cases, though. From the git repo, it appears that
ReceiveChannel.isClosedForReceive
has existed for 4 years, so I'm surprised that it's still considered "experimental". How much longer before it's considered stable?
7 Views