findings: wasmparser case-folding gap extends to interface names - #246
Merged
Conversation
…the rules Upstream search (2026-08-25) found no existing wasm-tools/wasmtime issue for the case-folding gap. InterfaceName raw-compares like ResourceFunc, so test:i/x-y + test:i/x-Y validates everywhere too. CM#703 (post-pin) rewrote strongly-unique as canonicalize-then-compare — fold retained, conclusion unchanged. Cross-linked to #238.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Amends the tracker entry from #237 after checking upstream for existing coverage (there is none, as of 2026-08-25):
InterfaceNamehas the same raw-string derive asResourceFunc, sotest:i/x-y+test:i/x-Yin one scope validates in wasm-tools 1.247 / wasmtime 47 / our translator, against the spec's fold-all-names rule.