Skip to content

Expose wasm_exceptions engine option to Ruby#599

Merged
jbourassa merged 1 commit into
bytecodealliance:mainfrom
takahashim:expose-wasm-exceptions
May 20, 2026
Merged

Expose wasm_exceptions engine option to Ruby#599
jbourassa merged 1 commit into
bytecodealliance:mainfrom
takahashim:expose-wasm-exceptions

Conversation

@takahashim
Copy link
Copy Markdown
Contributor

Closes #598.

Adds a dispatch arm in hash_to_config so the existing wasmtime::Config::wasm_exceptions method becomes reachable from Engine.new.

Verification

The reproducer from #598, before:

without options      : Wasmtime::Error: Could not build module: failed to parse WebAssembly module
wasm_exceptions: true: ArgumentError: Unknown option: :wasm_exceptions

After:

without options      : Wasmtime::Error: Could not build module: failed to parse WebAssembly module
wasm_exceptions: true: OK

@jbourassa
Copy link
Copy Markdown
Collaborator

Thanks!

@jbourassa jbourassa merged commit 78965cd into bytecodealliance:main May 20, 2026
11 checks passed
@takahashim takahashim deleted the expose-wasm-exceptions branch May 21, 2026 01:51
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.

Engine.new doesn't expose wasm_exceptions

2 participants