-
-
Notifications
You must be signed in to change notification settings - Fork 36
Literal keys contents / values #1036
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
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.
Rather than defining the value of a literal, it's clearer if we define the string value of a literal.
That's a term that can be naturally used in the places referring to it, and more directly incorporates "string" as a qualifier for "value", a term that we've tried to avoid using unadorned.
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.
I like @eemeli's suggestions. I suggest rewording one of them, tho...
Merge @eemeli's suggestions plus the "forked" suggestion from Mark Co-authored-by: Eemeli Aro <[email protected]>
The **_<dfn>string value</dfn>_** of a _literal_ | ||
for _unquoted literals_ is the text content of that _literal_; | ||
or for _quoted literals_, the text content of that _literal_ | ||
after removing the enclosing `|` characters | ||
then unescaping any escaped characters. |
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 feels a bit clumsy, but not objectionably so.
See #1028