Fix malformed sig parsed as multi-target #819
Open
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 fixes a crash when Prism parses a malformed sig as a multi target node:
This is just an example that came out of the fuzzer, it's not specific to sigs, it's how Prism parses the comma in the malformed code:
Here, one of the
leftsis aHashNode(the{params…}part), which is obviously not valid.The fix I came up with, is to check each of the lefts and rights to ensure they are valid nodes, and otherwise just return an empty tree. I'm not 100% sure this is the best approach, and it's different to how the original parser handles it.
Original desugar tree:
Original errors:
Prism desugar tree:
Prism errors: