Stream: git-wasmtime

Topic: wasmtime / issue #12243 Deduplicate const-eval fast paths

Wasmtime GitHub notifications bot (Jan 05 2026 at 19:15):

fitzgen opened issue #12243:

https://github.com/bytecodealliance/wasmtime/pull/12234 introduced a new simple const-eval fast path. We already have one here. We didn't initially share them because the existing one is inside the wasmtime crate and uses wasmtime crate types, which can't be used from inside wasmtime-internal-cranelift. We should resolve this situation by adding traits or moving all of this into wasmtime-environ and adding a WasmValue enum to that crate or something.

---

Could this also get deduplicated with our preexisting fast path in const-eval?

_Originally posted by @alexcrichton in https://github.com/bytecodealliance/wasmtime/pull/12234#discussion_r2662277342_

Wasmtime GitHub notifications bot (Jan 05 2026 at 19:15):

fitzgen edited issue #12243:

https://github.com/bytecodealliance/wasmtime/pull/12234 introduced a new simple const-eval fast path. We already have one here. We didn't initially share them because the existing one is inside the wasmtime crate and uses wasmtime crate types, which can't be used from inside wasmtime-internal-cranelift. We should resolve this situation by adding traits or moving all of this into wasmtime-environ and adding a WasmValue enum to that crate or something.

---

Could this also get deduplicated with our preexisting fast path in const-eval?

_Originally posted by @alexcrichton in https://github.com/bytecodealliance/wasmtime/pull/12234#discussion_r2662277342_

Last updated: Jan 09 2026 at 13:15 UTC