Closed dcastro closed 1 year ago
Problem: Matching with RecordWildCards can be problematic.
RecordWildCards
It makes it harder to see where identifiers come from. E.g.:
f x y D{..} = z
Where does z`` come from? Is it a free variable? Or was it put in scope byD{..}`? It's not clear.
z`` come from? Is it a free variable? Or was it put in scope by
It also makes it hard to see where a variable is used in the definition of a function.
f x y z = < huge function definition >
If I want to know where and how x is used, I can just click it and my IDE will highlight all the places where x is used.
x
With D{..}, no such luck. I usually have to delete D{..} and then HLS will point me to where all the fields names no longer typecheck.
D{..}
Solution: Replace usages of RecordWildCards with the recently introduced OverloadedRecordDot or NamedFieldPuns.
OverloadedRecordDot
NamedFieldPuns
None
Tests
Documentation
Description
Problem: Matching with
RecordWildCardscan be problematic.It makes it harder to see where identifiers come from. E.g.:
Where does
z`` come from? Is it a free variable? Or was it put in scope byD{..}`? It's not clear.It also makes it hard to see where a variable is used in the definition of a function.
If I want to know where and how
xis used, I can just click it and my IDE will highlight all the places wherexis used.With
D{..}, no such luck. I usually have to deleteD{..}and then HLS will point me to where all the fields names no longer typecheck.Solution: Replace usages of
RecordWildCardswith the recently introducedOverloadedRecordDotorNamedFieldPuns.Related issue(s)
None
:white_check_mark: Checklist for your Pull Request
Related changes (conditional)
Tests
Documentation
Stylistic guide (mandatory)