Zigzag construction of identity types of pushouts#1370
Closed
VojtechStep wants to merge 34 commits into
Closed
Conversation
Collaborator
Author
|
I just pushed the solution to the the last hole, making this the first complete proof of correctness of the zigzag construction. 🎉 As noted in the PR description there's still quite some work necessary to make it mergeable, but the formal result is 100% there. I'll be a little self indulgent and give this the 🏆 milestone 🏆 label. |
Collaborator
Author
|
As expected, the CI fails on insufficient memory |
e895fcb to
67ab1e9
Compare
Collaborator
Author
|
I bumped the heap size available to Agda, so the CI now has a chance to pass. This change should be reverted before merging |
Collaborator
Author
Well, that was unexpected... But at least the Ubuntu run passed |
Collaborator
|
It's 2025, and Haskell can't even handle a zigzag construction 🙄 smh 😤 |
Collaborator
Author
|
I know, right? "Strange closure type"? Buddy, the closures here can get way freakier |
Even macOS runners have 14GB of RAM, so this might just go through CI?
67ab1e9 to
18aabd9
Compare
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
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.
There are still two holes left to fill, but they seem to be conceptually easy enough that I'm confident publishing this draft PR now — in particular they don't have any important coherence content, and they should be provable from very general path algebra; essentially I need to (freely) give a homotopy which fits into a coherence diagram with variousis-section-map-inv-equivs,is-retraction-map-inv-equivs,preserves-trs etc.What needs to be done:
functoriality-stuffandstuff-overhave a lot of ad-hoc developmentIdeally I'd also like to avoid relying on the computation of
map-eq-transpose-equiv', which at leastcompute-square-over-zigzag-square-over-colimit-iddoes