Skip to content

Reserve the namespace for future keywords #482

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

Closed
aphillips opened this issue Sep 19, 2023 · 0 comments · Fixed by #529
Closed

Reserve the namespace for future keywords #482

aphillips opened this issue Sep 19, 2023 · 0 comments · Fixed by #529
Labels
syntax Issues related with syntax or ABNF

Comments

@aphillips
Copy link
Member

Our new stability policy mentions the possibility of future keywords. We should reserve a space for keywords to be defined later.

For the keywords themselves I would propose:

; reserved keywords are 2 to 8 lowercase ASCII letters
; keywords might be preceded by a starter sigil
; if we define one, it should be defined by the containing production
reserved-keyword = [2*8](%61-%7A)

For their integration, I would incorporate their use into declarations and body, but things are in flux to such an extent that we should wait for those specific changes.

@aphillips aphillips added the syntax Issues related with syntax or ABNF label Sep 19, 2023
@eemeli eemeli linked a pull request Nov 29, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
syntax Issues related with syntax or ABNF
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant