Skip to content

findings: wasmparser skips case-folding on [method]/[static] names - #237

Merged
lannbot merged 1 commit into
mainfrom
i185-wasmparser-finding
Aug 23, 2026
Merged

findings: wasmparser skips case-folding on [method]/[static] names#237
lannbot merged 1 commit into
mainfrom
i185-wasmparser-finding

Conversation

@lannbot

@lannbot lannbot commented Aug 23, 2026

Copy link
Copy Markdown
Collaborator

Tracker entry only (no code). Found while validating #185 against the component-model spec and wasm-tools/wasmtime.

Explainer.md §Name Uniqueness requires strongly-unique comparison (fold acronym case, strip the [...] prefix) and explicitly lists [method]foo.BAR vs [method]foo.bar as a validation error — but wasmparser's ResourceFunc compares the raw a.b string, so method/static case-collisions validate in wasm-tools 1.247, wasmtime 47, and our translator-shim alike (plain-label and record-field folded collisions are correctly rejected via KebabStr).

Full validation record: #185 (comment)

Recorded while validating #185 against the spec and wasm-tools/wasmtime:
Explainer.md's strongly-unique rule folds acronym case before comparing
extern names (its own example rejects [method]foo.BAR next to
[method]foo.bar), but wasmparser's ResourceFunc derives Eq/Hash on the
raw string, so method/static case-collisions validate everywhere our
pipeline looks. Candidate bytecodealliance/wasm-tools issue; filing is
the operator's call.
@lannbot
lannbot enabled auto-merge (squash) August 23, 2026 03:26
@lannbot
lannbot merged commit 40b3c32 into main Aug 23, 2026
4 checks passed
@lannbot
lannbot deleted the i185-wasmparser-finding branch August 23, 2026 16: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.

2 participants