Any word when `Flow` and associated API's are like...
# coroutines
d
Any word when
Flow
and associated API's are likely to leave 'experimental'? Is it too bad to admit I've got production code peppered with Experimental annotations? At least I haven't found bugs with it yet! 😅
e
Most of it is already stable (non-experimental) in
1.3.0
. Some operators are still being stabilized. Which one are you interested in, in particular?
s
Sorry to hijack the thread, but the one I would be interested are
Publisher<T>.asFlow()
,
Flow<T>.asFlux()
(since we are forced to publish experimental APIs due to these extensions experimental status).
d
Same;
.asFlow()
is one we are using a lot.
e
These are on track to be stable soon, no planned changes or know problems so far.
👍 3