Specify private reserved sigils ^ and &
#404
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aphillips
requested changes
Jun 30, 2023
| ; and for future specification versions | ||
| reserved = ( future-start / private-start ) reserved-body | ||
| future-start = "!" / "@" / "#" / "%" / "*" / "<" / ">" / "?" / "~" | ||
| private-start = "^" / "&" |
There was a problem hiding this comment.
We should discuss as a group which characters to reserve for private use, although these seem as good as any.
eemeli
commented
Jul 2, 2023
eemeli
commented
Jul 2, 2023
Co-authored-by: Addison Phillips <[email protected]>
|
Renamed |
aphillips
approved these changes
Jul 2, 2023
|
I added |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #378
This PR marks the
^and&reserved sigils as available for implementation use, as opposed to being reserved for future spec versions. Language is also added to clarify the distinction.Of the sigils remaining for future spec versions,
!/?and</>seem like potential matching pairs of some sort,#could be a comment or section introducer (perhaps paired with/), and*already has a meaning as a catch-all key. That leaves the following semantically unburdened "generic" sigils:@,%, and~. This should be sufficient for future expansion before we really need a 3.0.