[ refactor ] make Relation.Binary.Morphism.Definitions obsolete
#2922
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
This was referenced Jan 24, 2026
jamesmckinna
commented
Jan 26, 2026
| open import Relation.Binary.Core using (_Preserves_⟶_) | ||
| open import Relation.Binary.Bundles using (Setoid; Preorder; Poset) | ||
| open import Relation.Binary.Consequences using (mono⇒cong) | ||
| open import Relation.Binary.Definitions using (Monotonic₁) |
Collaborator
Author
There was a problem hiding this comment.
NB, this too could be replaced by
Suggested change
| open import Relation.Binary.Definitions using (Monotonic₁) | |
| open import Function.Definitions using (Congruent) |
But at the cost of straying outside the Relation.* hierarchy...
jamesmckinna
requested review from
JacquesCarette,
MatthewDaggitt and
gallais
and removed request for
JacquesCarette
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This tackles the first part of #2875 , retaining the module solely for compatibility per #1206 / #1213 as requested by @pnlph , so no actual
deprecationat this stage.Knock-on consequences include:
Function.Definitionsvs. alternativesHomomorphic₂throughout byFunction.Definitions.Congruent(but the name is still exported aspublicby the obsolete stub; and hence also exported byRelation.Binary.Morphism, but this could be removed/deprecated?)TL;DR: the 'cause' of the problem is yet again [ DRY ] with some basic concepts duplicated across the
Function/Relation/Algebrahierarchies as various specialisations (or not even that) of 'common' (very) general abstractions (eg 'monotonicity'/'congruence'/'respects') which different authors have, at different times, identified asCoreto one or other hierarchy... cf. #2917