Skip to content
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

[wgsl] Functions section defines WGSL builtins as always being available. #4474

Open
dj2 opened this issue Jan 31, 2024 · 0 comments
Open

[wgsl] Functions section defines WGSL builtins as always being available. #4474

dj2 opened this issue Jan 31, 2024 · 0 comments
Assignees
Labels
copyediting Pure editorial stuff (copyediting, *.bs file syntax, etc.) wgsl WebGPU Shading Language Issues

Comments

@dj2
Copy link
Member

dj2 commented Jan 31, 2024

In the Functions section of the spec we say: A built-in function is provided by the WGSL implementation, and is always available to a WGSL module. While this was true historically, it is no longer technically true.

If I've shadowed one of the builtin names, then that builtin is no longer available to be used. So, the builtin is only available if it is not shadowed. This will change after we have namespaces but it would be useful to clarify that portion of the spec and we can update it when/if namespaces land.

@dj2 dj2 added the wgsl WebGPU Shading Language Issues label Jan 31, 2024
@dneto0 dneto0 self-assigned this Jan 31, 2024
@dneto0 dneto0 added the copyediting Pure editorial stuff (copyediting, *.bs file syntax, etc.) label Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
copyediting Pure editorial stuff (copyediting, *.bs file syntax, etc.) wgsl WebGPU Shading Language Issues
Projects
None yet
Development

No branches or pull requests

2 participants