Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yoneda is broken #396

Open
tetrapharmakon opened this issue Sep 11, 2023 · 6 comments
Open

Yoneda is broken #396

tetrapharmakon opened this issue Sep 11, 2023 · 6 comments

Comments

@tetrapharmakon
Copy link
Contributor

The following code containing only a few imports

open import Categories.Category.Core 
open import Level

module Categories.Adjoint.Duploid {o l e} {C D : Category o l e} where

open import Categories.Functor
open import Categories.Functor.Properties
open import Categories.NaturalTransformation
open import Categories.Adjoint
open import Categories.Adjoint.Properties using (adjoint⇒monad; adjoint⇒comonad)
import Categories.Morphism.Reasoning as MR

yields an error

src/Categories/Yoneda.agda:80,25-43
Functor.F₁ F (Category.id C.op) ⟨$⟩ _x_256 != η y a ⟨$⟩ id of type
Setoid.Carrier (Functor.F₀ F a)
when checking that the expression F.identity SE.refl has type
(Functor.F₀ F a Setoid.≈ η y a ⟨$⟩ id) x

More precisely, importing Categories.Adjoint.Properties raises the problem.

On a different machine, a few hours before, a similar error was thrown (same file, but different: it said that yoneda-inverse didn't have the fields f, f^{-1}, etc, but instead to, from, to-cong, from-cong and inverse). Considering the issue is present on two different machines, I doubt this has to do with my local version of the repo, so... what happened?

@JacquesCarette
Copy link
Collaborator

Wild guess (don't have time to look at the details right now): you have a different version of stdlib. 1.7 and 2.0 are very different, and agda-categories only works for sure with 1.7. There's a PR with 2.0 compatibility, but it won't get pulled in until 2.0 is shipped.

@tetrapharmakon
Copy link
Contributor Author

It is very likely. I indeed have 2.0 on both machines... So it's me! Good to know.

@JacquesCarette
Copy link
Collaborator

You might be able to pull PR #452 into your development, and that might work. Or revert to 1.7.

@tetrapharmakon
Copy link
Contributor Author

You probably mean #352 but it seems I can't pull it locally (it's a work in progress)

@JacquesCarette
Copy link
Collaborator

Typo, yes. git merge the commits?

@JacquesCarette
Copy link
Collaborator

So can I close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants