Bringing the spec description in sync with the abnf #447
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
|
You're not wrong. Note the changes in #441 and the move towards defining standalone/opening/closing "elements", which should properly be termed expression. |
|
I think this is blocked by #441, and I'd really rather not introduce further increases to its scope from its current rather massive extent, but discuss changes like this after that PR has been merged. |
|
Per teleconference, please refector to fit in the syntax.md file and then ping me to merge. |
eemeli
requested changes
Sep 2, 2023
|
Replaced by #466 |
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.
The
.abnfis now this:In
{b :html}the:htmlis the function, notb(similar to{43 :number}and{|20231217T1930| :datetime})