Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fallback resolution should check private-use and reserved annotations for a leading name-like token #546

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.

Sign up for GitHub

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

Jump to bottom
Closed
gibson042 opened this issue Nov 29, 2023 · 2 comments
Closed

Fallback resolution should check private-use and reserved annotations for a leading name-like token #546

gibson042 opened this issue Nov 29, 2023 · 2 comments
Labels
resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. syntax Issues related with syntax or ABNF

Comments

@gibson042
Copy link
Collaborator

gibson042 commented Nov 29, 2023 •
edited
Loading

Originally posted by @gibson042 in #539 (comment) and #529 (comment)

Suggested refactor, to be coupled with checking in Fallback Resolution for reserved-body-name such that e.g. {@reserved} and {@reserved ||} resolve to the fallback value @reserved while {@reserved||} and {@reserved\\} and {@reserved{}} (if syntactically valid) resolve to �:

-reserved-body  = *( [s] 1*(reserved-char / reserved-escape / quoted))
+; reserved-body is a possibly-empty sequence of space-separated parts,
+; optionally starting with a name-like `reserved-body-name` used in fallback resolution
+reserved-body       = [(reserved-body-name / [s] reserved-body-start) *(s reserved-body-part) [s]]
+reserved-body-name  = 1*name-char
+reserved-body-start = *name-char (non-name-char / reserved-escape / quoted) [reserved-body-part]
+reserved-body-part  = 1*(reserved-char / reserved-escape / quoted)
+non-name-char       = %x21-2C        ; omit - .
+                    / %x2F           ; omit digits and :
+                    / %x3B-40        ; omit uppercase letters
+                    / %x5B           ; omit \
+                    / %x5D-5E        ; omit _
+                    / %x60           ; omit lowercase letters and { | }
+                    / %x7E-D7FF      ; omit surrogates
+                    / %xE000-10FFFF
+reserved-char       / %x00-08        ; omit HTAB and LF
+                    / %x0B-0C        ; omit CR
+                    / %x0E-19        ; omit SP
+                    / non-name-char / ALPHA / DIGIT / "-" / "." / ":" / "_"
This was referenced Nov 29, 2023
Merged
Merged
@aphillips aphillips added the syntax Issues related with syntax or ABNF label Dec 1, 2023
@eemeli eemeli added the resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. label Dec 12, 2023
@eemeli
Copy link
Collaborator

eemeli commented Dec 12, 2023

As I recall, we ended up determining during last week's call that this level of introspection should not be done, and that only the sigil would be used in the default fallback representation.

@gibson042
Copy link
Collaborator Author

Yes, I think this was resolved by #539.

@gibson042 gibson042 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. syntax Issues related with syntax or ABNF
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aphillips @eemeli @gibson042