-
Notifications
You must be signed in to change notification settings - Fork 265
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
Future of old syntax for local.get
or global.set
#1164
Labels
good first issue
Good for newcomers
Comments
local.get
or global.set
?local.get
or global.set
I don't believe any plans exist yet to phase out the old syntax, but it hasn't been the primary syntax in so long I think it'd be fine to delete all the old syntax at any time now. Would you be up for sending a PR to delete the old syntax? |
alexcrichton
added a commit
to alexcrichton/wasm-tools
that referenced
this issue
Aug 25, 2023
Long ago instructions like `get_local` were renamed to `local.get` along with a number of other instructions. The `wast` crate has for quite some time supported parsing the old forms but `wasmprinter` has always printed out the most "up to date" forms. This commit goes through and deletes the parsing support for all the old forms, meaning that it's now an error to use such syntax. Closes bytecodealliance#1164
alexcrichton
added a commit
that referenced
this issue
Aug 25, 2023
Long ago instructions like `get_local` were renamed to `local.get` along with a number of other instructions. The `wast` crate has for quite some time supported parsing the old forms but `wasmprinter` has always printed out the most "up to date" forms. This commit goes through and deletes the parsing support for all the old forms, meaning that it's now an error to use such syntax. Closes #1164
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, two versions of syntax for some instructions exist, e.g.
local.get
andget_local
. Is there a plan to phase out the latter version?See also WebAssembly/spec#884
The text was updated successfully, but these errors were encountered: