Stream: git-wasmtime

Topic: wasmtime / PR #11557 Don't unwrap results of const-eval

Wasmtime GitHub notifications bot (Aug 28 2025 at 18:56):

alexcrichton opened PR #11557 from alexcrichton:no-unwrap-const-eval to bytecodealliance:main:

While all const expressions executed at runtime are valid they can still fail due to GC OOM or failure to allocate more GC memory. As a result all unwrap() on eval(...) is removed in favor of propagating upwards the result.

Closes #11469

<!--
Please make sure you include the following information:

• If this work has been discussed elsewhere, please include a link to that
  conversation. If it was discussed in an issue, just mention "issue #...".

• Explain why this change is needed. If the details are in an issue already,
  this can be brief.

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

Wasmtime GitHub notifications bot (Aug 28 2025 at 18:56):

alexcrichton requested pchickey for a review on PR #11557.

Wasmtime GitHub notifications bot (Aug 28 2025 at 18:56):

alexcrichton requested wasmtime-core-reviewers for a review on PR #11557.

Wasmtime GitHub notifications bot (Aug 28 2025 at 19:50):

fitzgen submitted PR review:

Thanks!

Wasmtime GitHub notifications bot (Aug 28 2025 at 20:31):

fitzgen merged PR #11557.

Last updated: Dec 06 2025 at 07:03 UTC