-
Notifications
You must be signed in to change notification settings - Fork 362
Open
Labels
copyeditingPure editorial stuff (copyediting, *.bs file syntax, etc.)Pure editorial stuff (copyediting, *.bs file syntax, etc.)wgslWebGPU Shading Language IssuesWebGPU Shading Language Issues
Description
Why does the WGSL spec language in sections like §8.11 Variable Identifier Expression use the phrasing "X is an identifier resolving to an in-scope Y"? It looks like the spec's definition of "resolving" implies that when "X resolves to Y", Y must be in scope. This phrasing appears in several places.
This is a very minor problem (if it is indeed redundant at all). But when someone bothers to spell out that an identifier resolves specifically to an in-scope declaration, it makes me wonder if it's possible in other situations to have identifiers resolving to not-in-scope definitions, which seems like nonsense. It seems like we could improve the pragmatics of the spec a little bit by not spelling this out.
Metadata
Metadata
Assignees
Labels
copyeditingPure editorial stuff (copyediting, *.bs file syntax, etc.)Pure editorial stuff (copyediting, *.bs file syntax, etc.)wgslWebGPU Shading Language IssuesWebGPU Shading Language Issues