-
-
Notifications
You must be signed in to change notification settings - Fork 36
Implement private-use
separately from reserved
#421
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
Conversation
Note that I didn't address making reserved opaque.
Co-authored-by: Eemeli Aro <eemeli@mozilla.com>
Co-authored-by: Eemeli Aro <eemeli@mozilla.com>
Co-authored-by: Eemeli Aro <eemeli@mozilla.com>
Co-authored-by: Eemeli Aro <eemeli@mozilla.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current shape of the changes to the syntax looks fine to me. There are some changes to formattting.md
that should be applied at the same time, as its references to reserved need to be updated to also deal with private-use.
I missed this earlier.
- Else, the _expression_ has a _reserved_ _annotation_, | ||
an Unsupported Expression error is emitted and a fallback value is used as its value. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a run-on sentence, and the "it" could be specified a bit more explicitly. Yes, I realise that I'm in part correcting my own suggestion here.
- Else, the _expression_ has a _reserved_ _annotation_, | |
an Unsupported Expression error is emitted and a fallback value is used as its value. | |
- Else, the _expression_ has a _reserved_ _annotation_. | |
An Unsupported Expression error is emitted and | |
the expression resolves to a fallback value. |
1. [Private-Use Sequences](#private-use) | ||
2. [Reserved Sequences](#reserved) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to start using explicit <a name="foo"></a>
anchors at some point, rather than having two different names for spec sections.
reserved
to suitNote that I did not include changing
reserved
to use*(text)
in this PR, but did changeprivate-use
to do so.