[jnigen] Kotlin void suspend funcs now return Future<void> in Dart #2922
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unitis a singleton sentinel used by Kotlin when translating suspend funcs that returnvoidinto Java methods. It's needed because Java doesn't supportvoidas a generic type param, so various internal objects likeContinuation<T>are represented asContinuation<Unit>instead ofContinuation<void>.This PR special cases
Unitin the return type of a suspend function to code gen asFuture<void>instead ofFuture<JObject>. Same for interfaces with void suspend functions.Ordinary functions that return
voidare translated directly into Java methods that returnvoid, so already returnvoidin Dart land. Also,Unitis a real object, so it could conceivably be passed as a param to a method etc. So this special casing should only be applied to the return type of suspend functions.Fixes #2876