Skip to content
New issue

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

Bump crate versions #616

Merged
merged 2 commits into from May 19, 2022
Merged

Bump crate versions #616

merged 2 commits into from May 19, 2022

Conversation

alexcrichton
Copy link
Member

To help facilitate development of the component model in Wasmtime itself
I wanted to release the current implementation of components in *.wast
plus recent fixes for wasmparser/wasmprinter/etc. This'll all continue
to change but publishing the current state should help unblock the
Wasmtime changes.

To help facilitate development of the component model in Wasmtime itself
I wanted to release the current implementation of components in `*.wast`
plus recent fixes for wasmparser/wasmprinter/etc. This'll all continue
to change but publishing the current state should help unblock the
Wasmtime changes.
Currently `(start $f)` fails to compile because the loop that parses
values expected a `(result ..)` to always be present, but it is not
alwyas guaranteed to be present.
@alexcrichton alexcrichton merged commit fcb052f into bytecodealliance:main May 19, 2022
@alexcrichton alexcrichton deleted the bump branch May 19, 2022 18:27
code-terror pushed a commit to code-terror/wasm-tools that referenced this pull request Aug 24, 2022
* Bump crate versions

To help facilitate development of the component model in Wasmtime itself
I wanted to release the current implementation of components in `*.wast`
plus recent fixes for wasmparser/wasmprinter/etc. This'll all continue
to change but publishing the current state should help unblock the
Wasmtime changes.

* Fix a failing test on `main`

Currently `(start $f)` fails to compile because the loop that parses
values expected a `(result ..)` to always be present, but it is not
alwyas guaranteed to be present.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants