-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is fun <T> (suspend () -> T).asFlow(): Flow<T>
still marked as @FlowPreview
?
#3542
Comments
BTW, I can see the more primitive way is actually shorter, so that might be part of the answer?
|
I have created #3097 |
|
override fun observeIsTyping(): Flow = public fun <T> (() -> TypeVariable(T)).asFlow(): Flow<TypeVariable(T)> defined in kotlinx.coroutines.flow public fun <T> Array<TypeVariable(T)>.asFlow(): Flow<TypeVariable(T)> defined in kotlinx.coroutines.flow public fun IntArray.asFlow(): Flow<Int> defined in kotlinx.coroutines.flow public fun LongArray.asFlow(): Flow<Long> defined in kotlinx.coroutines.flow public fun <T> Iterable<TypeVariable(T)>.asFlow(): Flow<TypeVariable(T)> defined in kotlinx.coroutines.flow public fun <T> Iterator<TypeVariable(T)>.asFlow(): Flow<TypeVariable(T)> defined in kotlinx.coroutines.flow public fun IntRange.asFlow(): Flow<Int> defined in kotlinx.coroutines.flow public fun LongRange.asFlow(): Flow<Long> defined in kotlinx.coroutines.flow public fun <T> Sequence<TypeVariable(T)>.asFlow(): Flow<TypeVariable(T)> defined in kotlinx.coroutines.flow public fun <T> BroadcastChannel<TypeVariable(T)>.asFlow(): Flow<TypeVariable(T)> defined in kotlinx.coroutines.flow public fun <T> (suspend () -> TypeVariable(T)).asFlow(): Flow<TypeVariable(T)> defined in kotlinx.coroutines.flow this is my issue solve it please |
Hello,
I just noticed the suspend function to Flow extension (
fun <T> (suspend () -> T).asFlow(): Flow<T>
) is still marked as@FlowPreview
.Is there a reason why?
My use case today was creating a combined flow where one of the inputs is a suspend function:
The text was updated successfully, but these errors were encountered: