Document grmtools section #499
Merged
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
ratmice
commented
Mar 10, 2025
ratmice
commented
Mar 10, 2025
ltratt
reviewed
Mar 11, 2025
ltratt
reviewed
Mar 11, 2025
Member
|
Please squash. |
ratmice
force-pushed
the
document_grmtools_section
branch
from
91794aa to
66553f6
Compare
Collaborator
Author
|
rustfmt + Squashed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds a pair of sections for extensions to lex/yacc, as kind of companion chapters to their respective compatibility chapters. I apologize in advance for being terrible at writing.
This also fixes a couple of issues I noticed when documenting the new
%grmtoolsstuff in the book.CTLexerBuilderfunction forallow_wholeline_commentsparse_escapeswas listed as aregexflag, but it is grmtools specific.