-
Notifications
You must be signed in to change notification settings - Fork 592
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.
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
Parser improvements from #756 #1625
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just minor things, or things I think should of been kept from #756.
"byte", | ||
"bool", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'd be nice to swap these like #756 did, and like this PR does in the keyword list.
It felt more logical to me to have all the numeric types together instead of bool
in the middle of them.
"byte", | |
"bool", | |
"bool", | |
"byte", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that you would have to also swap the order of the Kind
enumerators to match, since we depend on the ordering. But I think that the order should be swapped there anyways.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather leave this swap to another PR as I would need to update the code generators accordingly.
This PR applies the parser (including grammar) improvements from #756.
#756 also added new types (unsigned and varints), but this PR doesn't add them.