Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Name in enable directive can be a keyword or reserved word #2650

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 8, 2022
Merged

Name in enable directive can be a keyword or reserved word #2650

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions wgsl/index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6927,14 +6927,12 @@ Hypothetically, extensions could be used to:

An <dfn noexport>enable directive</dfn> indicates that the functionality
described by a particular named
[=extension=] may be used in the source text after the directive itself.
That is, language functionality described by the extension may be used in any
source text after the `enable` directive.
[=extension=] may be used.
The grammar rules imply that all enable directives must appear before any [=declarations=].

The directive must not appear inside the text of any [=declaration=].
(If it were a declaration, it would be at [=module scope=].)
The directive uses an [=identifier=], [=keyword=], or [=reserved word=] to name the extension.

The directive uses an [=identifier=] to name the extension, but does not
If the name is an identifier, the directive does not
create a [=scope=] for the identifier.
Use of the identifier by the directive does not conflict with the
use of that identifier as the name in any [=declaration=].
Expand Down