Skip to content

TODO: Experiment with Hints in derive.v #2069

Closed

Description

@affeldt-aist

@yosakaon made the following observation:

#2040 (comment)

This is about the following hint:

Hint Extern 0 (is_derive _ _ (fun x => _ *m _) _) => apply: is_derive_mulmx : typeclass_instances.

Activity

  1. added this to the 1.18.0 milestone on Jul 31, 2026
  2. yosakaon commented on Jul 31, 2026

    @yosakaon
    Contributor

    I don't know if it is the best course of action to add such a hint and if it might break (I don't think so) other developments but it works well in my current development. I can open a PR but I'd like to know if there is any "canonical" way to deal with such a problem (simple apply fails in harder goals -> use apply:). But unless this hint is in place afaik, typeclass inference will fail at solving such goals, which fails the objective of using is_derive in the first place and renders is_derive_mulmx pointless.

  3. yosakaon commented on Jul 31, 2026

    @yosakaon
    Contributor

    eapply is_derive_mulmx works as well in a compound goal.

  4. modified the milestones: 1.18.0, 1.19.0 on Aug 30, 2026
  5. affeldt-aist commented on Aug 30, 2026

    @affeldt-aist
    MemberAuthor

    Since PR #2017 seems inconclusive, shall we close this issue? (fyi: @CohenCyril )

  6. affeldt-aist commented on Sep 2, 2026

    @affeldt-aist
    MemberAuthor
  7. modified the milestones: 1.18.0, 1.19.0 on Sep 2, 2026
  8. yosakaon commented on Sep 2, 2026

    @yosakaon
    Contributor

    I think it's ok to close

  9. affeldt-aist commented on Sep 2, 2026

    @affeldt-aist
    MemberAuthor

    Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    experiment 🧪This issue/PR is very experimental

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions