Add lexer for P4 #2049
Merged
Add lexer for P4 #2049
Conversation
This file contains 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
|
I have been using this for a couple of weeks now to good effect in an AsciiDoc version of the P4 language specification. I have already given the submitter comments earlier, which he has incorporated into this PR, so it looks good to me. |
|
@tancnle any chance we can work toward getting this in the next release? |
|
Thank you for your work on this PR @rcgoodfellow. LGTM 🚀 |
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.
This PR adds support for the P4 language.
There has been a bit of discussion and use of this lexer in the P4 community here: p4lang/p4-spec#1115 (comment).