Add a diagnostic triggered when a pipeline-constant is set for an override in the shader module that is not used by the entry point #4643
Labels
wgsl
WebGPU Shading Language Issues
Milestone
This is forked from #4624
During pipeline creation time, it is valid for a pipeline constant to be set for an override that exists in the shader but is not statically accessed by the entry point.
In the discussion from #4624 we agreed it would be nice to add a diagnostic, defaulting to
off
that would trigger in this case.It's an extra guardrail that the developer can opt into.
To be determined:
The text was updated successfully, but these errors were encountered: