Add Odin lexer #802
Merged
Add Odin lexer #802
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
Adds the odin.xml rules for a lexer along with odin.actual and odin.expected Should handle the majority of Odin syntax well enough including nested comments. However for now I have just left attributes as one token rather than sub-parsing the @(x = y) to be multiple tokens
These upated when I was generating odin.expected. I am not sure if it is better to update these as well or leave it so I figured I would leave for now
Odin has a number of other built in integer types that are not in most other languages. Make sure those are included
alecthomas
approved these changes
Jul 19, 2023
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.
Adds the odin.xml rules for parsing Odin syntax along with odin.actual and odin.expected
Should handle the majority of Odin syntax well enough including nested comments. Currently, I have attributes as one token rather than sub-lexing the
@(x = y)as it's a couple different optional cases.I think I followed the lexers/README.md properly but let me know if not