Refactor crate features for more control over hash-maps usage #1265
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 allows to drop some
wasmi_collections
dependencies when unused for improved compile times.Usage
Wasmi users who previously used
no-hash-maps
should simply useprefer-btree-collections
now instead to make sure to always use btree-based collections in their compiled artifacts.Summary
no-hash-maps
crate feature. Also remove it fromdefault
feature set.hash-collections
crate feature.prefer-btree-collections
crate feature.Feature/collections usage matrix:
hash-collections
prefer-btree-collections
Similar to: https://github.com/bytecodealliance/wasm-tools/pull/1866/files
Will be even more useful once #1141 has been merged.
Benchmarks
dev
)release
)