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

Remove feature validation from Wasmtime #9623

Merged

Conversation

alexcrichton
Copy link
Member

Some of this originated in #917 but nowadays it shouldn't be necessary to control proposals like this. Instead it's probably best nowadays to throw configuration at wasmparser and use its definition of features to determine whether constructs make sense or not. This reduces the amount of bits and pieces Wasmtime has to do and avoids interactions such as #9622.

Closes #9622

Some of this originated in bytecodealliance#917 but nowadays it shouldn't be necessary
to control proposals like this. Instead it's probably best nowadays to
throw configuration at `wasmparser` and use its definition of features
to determine whether constructs make sense or not. This reduces the
amount of bits and pieces Wasmtime has to do and avoids interactions
such as bytecodealliance#9622.

Closes bytecodealliance#9622
@alexcrichton alexcrichton added this pull request to the merge queue Nov 19, 2024
Merged via the queue into bytecodealliance:main with commit dab9dc8 Nov 19, 2024
40 checks passed
@alexcrichton alexcrichton deleted the remove-feature-validation branch November 19, 2024 18:32
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.

Config::wasm_bulk_memory(false) cannot be usefully specified without enabling the gc feature.
3 participants