fix: use correct expr positions when delaborating match
patterns
#4034
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.
In the following, hovering over
true
in the infoview was showingNat.succ y
.Now hovering over
true
showstrue
.The issue was that SubExpr positions were not being tracked for patterns, and the position for a pattern could coincide with the position for a RHS, putting overwriting terminfo. Now the position given to a pattern is correct and unique.
Refactors the
match
delaborator, makes it handle shadowing ofh :
discriminant annotations correctly, and makes it use the standardwithOverApp
combinator to handle overapplication.