wasmtime-wasi
usability: re-exports of common siblings
#2776
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.
Until more impls come along, every user of
wasmtime-wasi
is going to usewasi-cap-std-sync
as theirWasiCtxBuilder
. Rather than make our users track a dependency on an additional crate, re-export it under the top-levelsync
module.This re-export sits behind the
sync
Cargo feature, which is enabled by default. Users who want to opt out of these re-exports can disable default-features.Additionally,
wasi-cap-std-sync
now re-exports thecap_std::fs::Dir
type that it consumes inWasiCtxBuilder::preopened_dir
. Again, just keeps the consumers of these crates from tracking another dep version.And finally I cleaned up those extra deps for the wasmtime cli.