-
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
awaitSingleOrNull returns not nullable value #2591
Labels
Comments
dkhalanskyjb
added a commit
that referenced
this issue
Mar 30, 2021
This was referenced Mar 30, 2021
dkhalanskyjb
added a commit
that referenced
this issue
Apr 5, 2021
Note that we also fixed the corresponding |
dkhalanskyjb
added a commit
that referenced
this issue
Apr 7, 2021
dkhalanskyjb
added a commit
that referenced
this issue
Apr 9, 2021
dkhalanskyjb
added a commit
that referenced
this issue
Apr 16, 2021
dkhalanskyjb
added a commit
that referenced
this issue
Apr 20, 2021
dkhalanskyjb
added a commit
that referenced
this issue
Apr 21, 2021
pablobaxter
pushed a commit
to pablobaxter/kotlinx.coroutines
that referenced
this issue
Sep 14, 2022
…nd Maybe (Kotlin#2628) * Deprecated `awaitSingleOr*` on arbitrary Publishers * Added specialized `awaitSingle` and `awaitSingleOrNull` methods on `Maybe<T>` and `Mono<T>` * Deprecated `Maybe<T>.await()` in favor of `Maybe<T>.awaitSingleOrNull()` * Added specializations of most of the `await*` methods for `Mono<T>` and deprecated them, as the only useful methods on `Mono<T>` are `awaitSingle` and `awaitSingleOrNull` * Reworded some documentation for `await*` methods Fixes Kotlin#2591 Fixes Kotlin#1587
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
kotlinx.coroutines/reactive/kotlinx-coroutines-reactive/src/Await.kt
Line 107 in edd584a
awaitSingleOrNull returns not nullable value and
Also, behaviour differs from the std function:
The text was updated successfully, but these errors were encountered: