We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Probably because WebAssembly/component-model#384 was merged a few weeks before WebAssembly/component-model#405 , the component model binary specification defines futures as 0x65 and error-contexts as 0x64.
Wasm-tools on the other hand uses future 0x67 and error-context 0x65. I guess the implementation predates the spec.
Both agree on streams as 0x66.
I can create a PR to make wasm-tools follow the spec, but I would like to clarify that this is indeed the right path.
PS: I found this problem while implementing fixed size lists in #1992 ...
The text was updated successfully, but these errors were encountered:
Solve the future/errror binary spec discrepancy, fixes bytecodeallian…
9094a95
…ce#2044
61300c8
Solve the future/errror binary spec discrepancy, fixes #2044 (#2045)
823efcb
Fixed in #2045
Sorry, something went wrong.
No branches or pull requests
Probably because WebAssembly/component-model#384 was merged a few weeks before WebAssembly/component-model#405 , the component model binary specification defines futures as 0x65 and error-contexts as 0x64.
Wasm-tools on the other hand uses future 0x67 and error-context 0x65. I guess the implementation predates the spec.
Both agree on streams as 0x66.
I can create a PR to make wasm-tools follow the spec, but I would like to clarify that this is indeed the right path.
PS: I found this problem while implementing fixed size lists in #1992 ...
The text was updated successfully, but these errors were encountered: