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
-- Respecting - relatedness is preserved on both sides by equality_Respects₂_ : Rel A ℓ₁ → Rel A ℓ₂ →Set _
P Respects₂ _∼_ = (P Respectsʳ _∼_) × (P Respectsˡ _∼_)
has
left component the proof of _Respectsʳ_
right component that of _Respectsˡ_
This seems a like bug (cognitive dissonance at the very least). Worth fixing?
The text was updated successfully, but these errors were encountered:
One way to tackle breaking would be to have an interim v2.2-badged PR which introduces, say, _Respects²_, and deprecates _Respects₂_ in its favour, ahead of agreeing a/the 'right' name (possibly the original? I'm not thrilled by it...) for v3.0?
Hmm while this would be one possible route, it would end up with us breaking the convention of always using subscripts to indicate arity. I think better to make the breaking change rather than end up in an unsatisfactory situation...
jamesmckinna
added a commit
to jamesmckinna/agda-stdlib
that referenced
this issue
Dec 9, 2024
The definition:
has
_Respectsʳ_
_Respectsˡ_
This seems a like bug (cognitive dissonance at the very least). Worth fixing?
The text was updated successfully, but these errors were encountered: