-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Make WasiCtx
overridable
#3895
Make WasiCtx
overridable
#3895
Conversation
@pchickey Any chance this can land in tomorrow's release? We'd hate to lose a month on this. |
If @alexcrichton is ok holding up the release I am happy to get this in |
Subscribe to Label Actioncc @kubkon
This issue or pull request has been labeled: "wasi"
Thus the following users have been cc'd because of the following labels:
To subscribe or unsubscribe from this label, edit the |
Sorry, didn't account for case with multiple bounds (when |
73d0442
to
3ac1581
Compare
3ac1581
to
ea5ebee
Compare
In some use cases it is desirable to provide a custom snapshot WASI context. Facilitate this by depending on a combination of traits required rather than concrete type in the signature. Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
ea5ebee
to
adf702c
Compare
Should this be added to the 0.35.0 release notes? |
Sure if you'd like to send a PR I can take a look. |
This is a follow-up to bytecodealliance#3895, which landed after the release notes were written.
This is a follow-up to #3895, which landed after the release notes were written.
In some use cases it is desirable to provide a custom snapshot WASI
context. Facilitate this by depending on a combination of traits
required rather than concrete type in the signature.
This change allows for e.g. wrapping
WasiCtx
into a struct and providing custom implementations for traits