-
Notifications
You must be signed in to change notification settings - Fork 957
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.
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
Add directive keywords to error message for parsing global item #6723
base: trunk
Are you sure you want to change the base?
Add directive keywords to error message for parsing global item #6723
Conversation
6ca2422
to
40705ca
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, minus one issue.
Interestingly, the term "item" (from before this PR) is a Naga concept, rather than a standard WGSL one. 🤔 I had hoped to align the vocabulary at the same time as the issue was handled, but I notice that didn't communicate that. I'm happy to save that for a further iteration, or even drop the thought entirely; I don't think it's going to be a problem in practice. |
Notify the user that they can also use `diagnostic`, `enable`, or `requires` in this context.
e05096a
to
68ddfd0
Compare
Notify the user that they can also use
diagnostic
,enable
, orrequires
in this context.Connections
Addresses #6421.
Description
Support for directives has recently improved, so this error message now reflects that the user can also use directive keywords at the top-level.
Testing
Verified locally, did not add a test for this small change in accordance with the style of the tests in this module.
Checklist
cargo fmt
.taplo format
.cargo clippy
. If applicable, add:--target wasm32-unknown-unknown
--target wasm32-unknown-emscripten
cargo xtask test
to run tests.CHANGELOG.md
. See simple instructions inside file.