wit/bindgen: fix wasm-tools WIT generation bugs #287
Merged
Conversation
This file contains 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
These were previously swallowed.
This allows the use of use statements inside of inline interface imports.
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.
Errors from
wasm-toolswere being silently swallowed, masking a number of related issues:import foo:foo/flagswere not being escaped (foo:foo/%flags).wasm-toolsinvocations (in wasm) were being silently ignored. They are now logged and returned. Errors returned fromwasm-tools component embedare now fatal.wit/bindgennow supply a logger toGo().The synthetic world now uses the original WIT package, to allow inline
import foo: interface { ... }with inlineusestatements that refer to other interfaces or worlds in the same package.Fixes #281.