-
Notifications
You must be signed in to change notification settings - Fork 246
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
Redefine Algebra.Consequences.Setoid.wlog
#2626
Comments
I think we should find a use case of this function before refactoring it! IME it's utterly useless and I always had to resort to the more general It's not easy to explain, but people can get a feel for it by taking the |
A-ha!? Oops. |
Doesn't this actually argue for deleting this entirely? |
Arguably, yes, I guess so, but in the meantime, it would be interesting to investigate what might work instead, viz. conditions under which |
Open an issue? Because this one seems to be about something else. |
Well, maybe you're right, but having opened the original issue (in a simple minded, low energy local fix way ...) Guillaume's comment made me think some more about things, so it seemed 'in scope' for an issue about changing an existing definition... But it may indeed end up that the 'change' should involve deletion/deprecation. UPDATED: and indeed, as the |
The trouble with the definition:
is twofold:
≈-subst : Substitutive _≈_ p
is needlessly restrictive, when≈-resp : P Respects _≈_
would sufficeRelation.Binary.Definitions
, a relation_≈_
only ever satisfiesSubstitutive _≈_ p
when it isPropositionalEquality
(or a derivative of it), so theSetoid
version ofwlog
can only ever be deployed in thePropositional
case!Arguably this is
bug
, so should be fixed as non-backwards-compatible change in v2.3 ;-) but v3.0 is probably more reasonable, or at least, less unreasonable...Accordingly, propose instead:
with marginal knock-on consequences for the
Propositional
case (resp P
instead ofsubst
)The text was updated successfully, but these errors were encountered: