-
Notifications
You must be signed in to change notification settings - Fork 78
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
Fixes an issue related to prefix shared alternatives with nesting restrictions #1919
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -152,9 +152,13 @@ public void testListSharing(){ | |
|
||
public void testDoubleLeftNullable() { | ||
executeParser(new DoubleLeftNullable()); | ||
} | ||
} | ||
|
||
public void testDoubleRightNullable() { | ||
executeParser(new DoubleRightNullableWithPrefixSharing()); | ||
} | ||
|
||
public void testDoubleRightNullable() { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @arnoldlankamp why is this test not useful anymore? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's still there. This is just a tabs vs spaces formatting diff. |
||
executeParser(new DoubleRightNullableWithPrefixSharing()); | ||
} | ||
public void testPrefixSharedExcept() { | ||
executeParser(new PrefixSharedExcept()); | ||
} | ||
} |
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.
Propose to include the old constructor as well
@deprecated
, such that we can bootstrap without too many issues.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.
Adding a constructor with the old signature, which uses an empty
dontNest
map, would make the change backwards compatible and should make everything work as before.I considered this myself, but ultimately decided against it, since it (naturally) also retains the bug. Making this a breaking change forces people to regenerate any existing parsers and prevents them from continuing to use a deprecated/buggy version.
But feel free to add one if this is preferred.