You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is useful because it can give definitional computation laws for the inverse. It will take a large effort to refactor the greater library, but perhaps it is possible to start with a smaller refactoring to at least instate this as the default for future contributions. On the other hand, having two competing defaults may be detrimental to the quality and usability of the library, so we should discuss this rigorously before attempting to implement it.
The text was updated successfully, but these errors were encountered:
it would be very useful to implement #1030 before we undertake this refactoring. This will let us see if the refactoring leads to a performance improvement.
I'm ~just~ adding ~a little~ some infrastructure about coherently
invertible maps ref. our discussions ~yesterday~ the other day. Don't
worry, I'm not starting a huge refactoring project.
Relevant to #946 and #1021.
### Summary
- Add mirror file about coherence squares of homotopies after coherence
squares of identifications
- Add some core files for more streamlined proofs in other core files.
- Refactor some proofs for coherently invertible maps
- `is-emb-is-equiv` was actually a proof about coherently invertible
maps
- slightly improve readability of
`is-coherently-invertible-is-invertible`
- Prove the following (and corollaries) without "coherent replacement":
- a coherently invertible map is transpose coherently invertible
- the inverse of a coherently invertible map is coherently invertible
- composites of coherently invertible maps are coherently invertible
- coherently invertible maps are closed under homotopies
This is useful because it can give definitional computation laws for the inverse. It will take a large effort to refactor the greater library, but perhaps it is possible to start with a smaller refactoring to at least instate this as the default for future contributions. On the other hand, having two competing defaults may be detrimental to the quality and usability of the library, so we should discuss this rigorously before attempting to implement it.
The text was updated successfully, but these errors were encountered: