You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WGSL has a bunch of reserved words that could very well be module or folder names: common, external, impl, priv, public, std, type, wgsl to name a few. I would be quite sad if we couldn't make a package named std.
Only the else keyword leads to a LR(1) conflict: if () {} else can be either if() {} else {} or if() {} else::path::to::fn();. Other keywords are fine.
WGSL has a bunch of reserved words that could very well be module or folder names:
common
,external
,impl
,priv
,public
,std
,type
,wgsl
to name a few. I would be quite sad if we couldn't make a package namedstd
.WGSL also has a buch of reserved keywords. For example, Lygia has a WGSL module named const.
Should module names follow the same restrictions as declaration idents?
I don't see any serious downside to this, I vote for.
The text was updated successfully, but these errors were encountered: