Refactor the 'Categories.Object.Zero' module #252
Merged
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
Member
|
Wonderful. That's very cool. |
JacquesCarette
approved these changes
Feb 23, 2021
themar7777
approved these changes
Feb 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
As per @HuStmpHrrr's suggestion on #249, I've reworked the definition of zero objects to use
IsTerminalandIsInitial. I also made a couple of fixes to some rather silly mistakes I made when writing this module:Zerozeroto𝟘, to avoid conflicts withzerofromLevel,Data.Nat, and many others!¡and!so that their types now make sense:¡ : 𝟘 ⇒ A! : A ⇒ 𝟘While I was at it, I added some autoduality proofs about zero objects that I need for cokernels.