-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
Part of #652 Seems convenient for the AST/CST (to not need to unwrap another layer) but we lose the ability to test it as a named parser and the generated parser code gets a bit bloated, since we now inline the choice. Maybe it'd be better if we somehow allow to "outline" select enums in v2, like this one? @OmarTawfik
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,6 +20,7 @@ | |
|
||
- name: "Statement" | ||
kind: "Parser" | ||
inlined: true | ||
versioned: | ||
0.4.11: | ||
choice: | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,6 +20,7 @@ | |
|
||
- name: "YulStatement" | ||
kind: "Parser" | ||
inlined: true | ||
versioned: | ||
0.4.11: | ||
choice: | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Large diffs are not rendered by default.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.