[ add ] Data.Bool.contradiction fixing #2847
#2853
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
I would have bet a large amount of money that this name would cause a lot of clashes with the original |
MatthewDaggitt
approved these changes
Oct 31, 2025
JacquesCarette
approved these changes
Nov 11, 2025
Collaborator
Author
|
@andreasabel 's latest comment on #2847 nudges me towards abandoning this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
NB.
Whateveras conventional wrt ex falso-style typing inData.Emptyetc.contradiction, avoiding the OP's redundantBool-prefix (potentially already invoked in any usage context via qualifiedimport Data.Bool as Bool, if needed, to avoid name clash withRelation.Nullary.Negation.Core.contradiction)Not really to my taste, but offered as a challenge to my own stubbornness on such issues.