Polyfill ToWasmtimeResult and add eventually-necessary call sites
#12308
+70
−28
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 polyfills
wasmtime_internal_error::ToWasmtimeResultinwasmtime_environ, adds the cargo feature plumbing that will eventually connect to the"wasmtime_internal_error/anyhow"cargo feature but for now just configures this polyfill, and adds uses of the polyfill at all the sites that will be necessary once we swap outanyhowforwasmtime_internal_error. Currently, the polyfill is just an identity function, becausewasmtime::Result/wasmtime_environ::error::Resultis just another name foranyhow::Result. Once we do move away fromanyhow, however, that will no longer be the case, and these uses will do the necessary conversion.My goal with landing this as an incremental commit is to make it so that the actual commit that does the error crate swap out can be as close to just the
Cargo.tomldependency change, without any other code changes as much as possible. This, in turn, means that swap out should be super easy to revert, if necessary.