Refactor how error-context is modeled
#2060
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
This commit refactors how the `error-context` type in the async component model implementation is modeled within these crates. Previously it was listed as a "defined type" but the binary encoding and component model itself has it listed as a "primitive type". While mostly the same the distinction is subtle enough (e.g. around naming rules) that this commit refactors the wasm-tools crates to match the component model specification.
dicej
approved these changes
Feb 20, 2025
ydnar
added a commit
to bytecodealliance/go-modules
that referenced
this pull request
Mar 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 refactors how the
error-contexttype in the async component model implementation is modeled within these crates. Previously it was listed as a "defined type" but the binary encoding and component model itself has it listed as a "primitive type". While mostly the same the distinction is subtle enough (e.g. around naming rules) that this commit refactors the wasm-tools crates to match the component model specification.