-
Notifications
You must be signed in to change notification settings - Fork 738
Add a flag that constrains features to the W3C recommendation #1899
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
Comments
one nuance might be how this interacts with other flags. ex. if you specify The use case I have is around spec additions for features themselves. the spectests include modules that may compile differently depending on what's enabled or not. When adding support for one feature, it is helpful to not accidentally turn on others. |
Sure, sounds like a useful flag to have. I wonder if it would make sense to call it |
Either way seems reasonable to include. |
almost, just that mutable-globals snuck into 1.0 :p |
I see. In that case we can probably simply remove the option to disable mutable globals. |
Perhaps |
well yeah interesting.. as a runtime I think mutable globals are problematic and so it is helpful to disable them. --disable-all is 1.0 minus mutable globals and that's probably a better setting than --enable-1.0 for certain users. PS --enable-X.X indeed.. there's probably a time to temporarily add --enable-1.1-snapshot for interop when things get that progressed. |
Since this is a repo in the org for the W3C core recommendation, I think it is a fair ask to have a flag that constrains features to what's included in that, and no more. It will help with tracking https://github.com/WebAssembly/wabt#supported-proposals and make upgrades seamless.
I'm not asking for this to be by default turned on, rather to make it possible to achieve undoing all the flags that turn on things not in the recommended spec. Ex.
--enable-1.0
(please don't call whatever flag MVP as that's jargon and not a W3C version number).Ex. just like
enable-all
The text was updated successfully, but these errors were encountered: