Skip to content

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

Merged
merged 13 commits into from
Jul 24, 2023
Merged

Conversation

aphillips
Copy link
Member

  • creates a separate section in the syntax spec
  • creates a separate rule in abnf
  • adjusts the text in reserved to suit

Note that I did not include changing reserved to use *(text) in this PR, but did change private-use to do so.

aphillips and others added 7 commits July 13, 2023 09:16
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>
Copy link
Collaborator

@eemeli eemeli left a 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.

@aphillips
Copy link
Member Author

@eemeli noted:

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.

Done in 77ef04e.

@aphillips aphillips requested a review from eemeli July 16, 2023 16:08
@aphillips aphillips requested a review from eemeli July 17, 2023 19:13
Comment on lines +105 to +106
- Else, the _expression_ has a _reserved_ _annotation_,
an Unsupported Expression error is emitted and a fallback value is used as its value.
Copy link
Collaborator

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.

Suggested change
- 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.

Comment on lines +22 to +23
1. [Private-Use Sequences](#private-use)
2. [Reserved Sequences](#reserved)
Copy link
Collaborator

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.

@aphillips aphillips merged commit e0566bc into main Jul 24, 2023
@aphillips aphillips deleted the aphillips-private-use branch July 24, 2023 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants