Repository navigation
Add map and implements stabilization to the Wasmtime 11-05 agenda - #901
Merged
alexcrichton merged 1 commit intoNov 3, 2026
Merged
Conversation
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
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.
Adds an item to discuss enabling the component model
mapandimplementsfeatures by default:map. The issues raised in review (map<K, V>allocates memory before validating the guest pointer wasmtime#14810, ThewasmtimeCLI does not supportmap<K, V>wasmtime#14811, Duplicate keys inmap<K, V>leak handles wasmtime#14812, Themap<K, V>WIT type has no codegen tests wasmtime#14813) are now closed.implements. Its Fuzzed column is still ❌, so the question is whether it can be enabled without a dedicated fuzzer, as discussed in Fuzz the component model implements feature wasmtime#14802 and Note thatimplementsdoesn't need fuzzing wasmtime#14914.