functoriality of span pushouts #2145
Open
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
Signed-off-by: Ali Caglayan <[email protected]> <!-- ps-id: 72cd34ee-d78d-4080-b27d-29d014fb1a6c -->
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.
Functoriality of span pushouts are simpler than their pushout counterparts in that they have simpler data.
As discussed in #2144 we could also simplify the definition of SPushout, but we will hold off on that for now.
Regarding naming, the beta rule for
rechas two problems. Firstly the path constructor is calledspgluenotsglueand secondly we don't capitlize. I've done it this way to stay consistent with the_indanalogues, but I think it might be better to change both of them.