Skip to content

findings: park the wasmparser case-folding entry until the wasmtime 49 bump #247

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.

Sign up for GitHub

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

Merged
lannbot merged 1 commit into from
Aug 25, 2026
Merged

findings: park the wasmparser case-folding entry until the wasmtime 49 bump #247

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion upstream-component-model-repo-findings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,11 @@ entry on resolution — see git history.)
post-#703 Explainer.md before filing. Consequence for us: spec-invalid
method/static and interface-name case-collisions can reach the runtime's
conventions layer — one of the triggers tracked in #185; translator-side
enforcement is #238.
enforcement is #238. **Deferred 2026-08-25 (operator): parked until the
wasmtime 49 toolchain bump** — upstream is actively reworking this corner
post-#703, so re-verify the bundled wasmparser then (probes in #238); if it
folds, the bump closes #238 and this entry dies, otherwise implement
shim-side and re-raise the filing question.

[WebAssembly/component-model]: https://github.com/WebAssembly/component-model

Expand Down
Loading