-
Notifications
You must be signed in to change notification settings - Fork 247
[Refractor] contradiction over ⊥-elim in Data.*.Relation.Binary.Lex.*
#2671
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
Conversation
Data/Vec/Relation/Binary/Strict
Data/Vec/Relation/Binary/Strict
Data/Vec/Relation/Binary/Strict
Data.Vec.Relation.Binary.Lex.Strict
Suggest, however, also touching |
Discovered a relevant change which should be committed before proceeding.
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.
Additionally: fix Data.Vec.Relation.Binary.Lex.Core
as suggested in line with the rest of these PRs, and mutatis mutandis, Data.List.Relation.Binary.Lex.Strict
as well!
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.
Final narrowing(s)?
open import Data.Empty using (⊥)
open import Data.Unit.Base using (⊤; tt) can be streamlined to: open import Data.Unit.Base using (tt) and if you don't mind replacing |
Data.Vec.Relation.Binary.Lex.Strict
Data.*.Relation.Binary.Lex.*
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.
Yup, I think this will do fine.
Thanks for taking the trouble to cross-propagate changes between the List
and Vec
versions of these relations... interesting to see what's common and what's not!
cf. #2679
@JacquesCarette are you happy to approve and merge now? |
No description provided.