will channelFlow or callbackFlow be reaching Stabl...
# coroutines
r
will channelFlow or callbackFlow be reaching Stable anytime soon?
d
Not soon, but this is production ready. API may change in the future.
b
Experimental != Unstable -- it just means not finalized so they may experience a change in the future -- in which case, almost every experimental API was left with a bridge API to the finalized version with proper
@Deprecated
and
ReplaceWith
annotating
r
Thanks for the input guys. but the only problem is if you work in a large code base with many modules and developers. they may lead to a massive refactor. Or are you all saying the changes won't be breaking?
a
Binary compatibility is also a big concern here.