-
Notifications
You must be signed in to change notification settings - Fork 245
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
Eliminate many propositional equality imports #2002
Conversation
0af4850
to
ccd3c81
Compare
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.
I think all the alignment changes in Reflection.AST.*
suggest we should just do away with lining up the using
keywords.
Other than this stylistic remark, everything looks good except for one issue
(perhaps a merge conflict?).
Also please don't force push the changes if you make any, it'll be a lot easier to |
Co-authored-by: G. Allais <[email protected]>
* Eliminate many propositional equality imports * Fix merge conflict in Data.Bool.Properties Co-authored-by: G. Allais <[email protected]> --------- Co-authored-by: G. Allais <[email protected]>
* Eliminate many propositional equality imports * Fix merge conflict in Data.Bool.Properties Co-authored-by: G. Allais <[email protected]> --------- Co-authored-by: G. Allais <[email protected]>
* Eliminate many propositional equality imports * Fix merge conflict in Data.Bool.Properties Co-authored-by: G. Allais <[email protected]> --------- Co-authored-by: G. Allais <[email protected]>
Many of the remaining imports of
Relation.Binary.PropositionalEquality
use either_≗_
or→-to-⟶
. Moving_≗_
toRelation.Binary.PropositionalEquality.Core
feels like a clear win, except it's defined in a little bit of an indirect way that pulls in some more imports