Skip to content

Conversation

@ricochet
Copy link
Contributor

This is intended to catch invalid WIT like the one is this report early: bytecodealliance/wit-bindgen#1411

@ricochet ricochet requested a review from a team as a code owner November 22, 2025 00:09
@ricochet ricochet requested review from abrown and removed request for a team November 22, 2025 00:09
@ricochet ricochet force-pushed the fix/validate-case-insentive branch from 8812bbe to c60eda9 Compare November 24, 2025 02:54
Copy link
Member

@alexcrichton alexcrichton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I think this'll need to happen at the crates/wit-parser/src/resolve.rs layer, however, rather than during the "AST resolve" step. For example include could cause a conflict, and that can't be resolved until src/resolve.rs where at ast/resolve.rs it's perserved as just include without knowing what it points to.

I think that moving it over there might lose some span information, but that's ok. In general it should be pretty easy to move I'd hope, but if you run into trouble let me know. As another minor comment though could the validation of imports/exports be extracted to a helper to avoid duplicating the logic/error message too?

@ricochet ricochet force-pushed the fix/validate-case-insentive branch from c60eda9 to 88c56d9 Compare November 24, 2025 20:50
Copy link
Member

@alexcrichton alexcrichton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@alexcrichton alexcrichton added this pull request to the merge queue Nov 25, 2025
Merged via the queue into bytecodealliance:main with commit 0f3f212 Nov 25, 2025
34 checks passed
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