Conversation
Collaborator
Author
|
Disabled the lib workflow as its proving unreliable. |
This was referenced Feb 14, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Building on #3221 and #3213, this update concludes support for async implementations. You can now both consume and produce the four async interfaces defined by the Windows Runtime directly in Rust.
IAsyncActionIAsyncOperation<T>IAsyncActionWithProgress<P>IAsyncOperationWithProgress<T, P>As illustrated in #3221, if you happen to have a value ready to return, you can simply use the
readyfunction as follows:If you need to spin up a background thread to wait for or calculate the value to return, you can use the
spawnfunction as follows:While the
readyimplementations return immediately, thespawnimplementations will take the closure and pass it by value to the Windows thread pool. This is far more efficient and scalable than creating a new thread each timespawnis called.I have also included extensive tests for both
readyandspawnimplementations in this update.