Add async constructor & callback support for Dart bindings #102
+640
−181
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.
Finally taught the Dart bindings how to handle async functions. The runtime now keeps a handle map for Rust futures and foreign (Dart) futures; we generate static factory methods for async constructors, and callback interfaces can actually await their Dart implementations. I also cleaned up the dart_async fixture tests so they call those factories instead of pretending constructors can be async. This should address #66
Summary
uniffiRustCallAsyncand add sharedUniffiForeignFutureruntime glue (handle map, cancellation)dart_asyncfixture/tests to call the async factories (Megaphone.new_(),UdlMegaphone.new_(), etc.) and adjust timing expectationsTesting
cargo test -p dart_async