[ refactor ] Symmetry of Bijection as a consequence of properties of a given Surjective function
#2583
Conversation
This file contains 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
2 tasks
jamesmckinna
added
the
status: duplicate
JacquesCarette
approved these changes
Feb 14, 2025
|
@JacquesCarette which of this and #2569 do you prefer? We should (probably) only merge one of them... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Alternative version of #2569 which dispenses with much of the deprecation cruft, in favour of badging this as a
bugfix.No separate
module Sectionadded, in favour of folding everything into the definitions ofFunction.Structures.IsBijectionandFunction.Bundles.Bijection.NB. there may now be some further redundancy that could be pruned out: manifest fields, or
Properties?