Make core instance allocation an async function#11456
Closed
alexcrichton wants to merge 1 commit intobytecodealliance:mainfrom
Closed
Make core instance allocation an async function#11456alexcrichton wants to merge 1 commit intobytecodealliance:mainfrom
async function#11456alexcrichton wants to merge 1 commit intobytecodealliance:mainfrom
Conversation
This commit is a step in preparation for bytecodealliance#11430, notably core instance allocation, or `StoreOpaque::allocate_instance` is now an `async fn`. This function does not actually use the `async`-ness just yet so it's a noop from that point of view, but this propagates outwards to enough locations that I wanted to split this off to make future changes more digestable. Notably some creation functions here such as making an `Instance`, `Table`, or `Memory` are refactored internally to use this new `async` function. Annotations of `assert_ready` or `one_poll` are used as appropriate as well. For reference this commit was benchmarked with our `instantiation.rs` benchmark in the pooling allocator and shows no changes relative to the original baseline from before-`async`-PRs.
Member
Author
|
Alas should have remembered to run tests. Unfortunately this won't be able to land separately, I'll try to keep this as a separate commit though. |
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
1 participant
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.
This commit is a step in preparation for #11430, notably core instance allocation, or
StoreOpaque::allocate_instanceis now anasync fn. This function does not actually use theasync-ness just yet so it's a noop from that point of view, but this propagates outwards to enough locations that I wanted to split this off to make future changes more digestable.Notably some creation functions here such as making an
Instance,Table, orMemoryare refactored internally to use this newasyncfunction. Annotations ofassert_readyorone_pollare used as appropriate as well.For reference this commit was benchmarked with our
instantiation.rsbenchmark in the pooling allocator and shows no changes relative to the original baseline from before-async-PRs.