forked from bytecodealliance/wasm-tools
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update wasm-tools for the latest component model proposal changes (by…
…tecodealliance#703) * wasm-encoder: update for component model proposal changes. This commit updates `wasm-encoder` for the following component model proposal changes: * Removed the `unit` type (this changed the encoding byte for the rest of the value types). * Case types of variants are now optional. * `expected` is now `result` and the ok and error types are optional. * Function types can now have either a single unnamed type or a vector of named types for parameters/results. * wasmparser: update to latest component model spec changes. This commit updates `wasmparser` for the following component model proposal changes: * Removed the `unit` type (this changed the byte parsed for the rest of the value types). * Case types of variants are now optional. * `expected` is now `result` and the ok and error types are optional. * Function types can now have either a single unnamed type or a vector of named types for parameters/results. * Validation now requires named function parameters and results to be unique. * wasm-smith: update to the latest component model proposal changes. This commit updates `wasm-smith` for the following component model proposal changes: * Removed the `unit` type. * Case types of variants are now optional. * `expected` is now `result` and the ok and error types are optional. * Function types can now have either a single unnamed type or a vector of named types for parameters/results. * Removed `NamedType` and `OptionalNameType` as they were now used in singular locations; instead `RecordType` and `FuncType` now just store simple tuples. * wasmprinter: update for latest component model proposal changes. * Removed the `unit` type. * Types in variant cases are now optional. * Renamed `expected` to `result`. * Types in `result` are now optional. * Print multiple results in function types. * wasm-compose: update for latest component model proposal changes. This commit updates `wasm-compose` for the recent component model proposal changes: * Removed the `unit` type. * Changed how component functions are encoded. * `expected` is now `result`. * Types are now optional in variant cases. * Types are now optional in results. * wast: update to latest component model proposal changes. * Removed the `unit` type. * Variant case types are now optional. * Renamed `expected` to `result`. * `result` types are now optional. * Support for multi-return component functions. * Update tests for component model proposal changes. * wasm-smith: keep the `refines` name when encoding a variant.
- Loading branch information
1 parent
5cb7452
commit 63f8ab3
Showing
44 changed files
with
1,267 additions
and
879 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.