coq-club AT inria.fr

Subject: The Coq mailing list

List archive

Re: [Coq-Club] non-automatic type class resolution

From: Jonathan Leivent <jonikelee AT gmail.com>
To: coq-club AT inria.fr
Subject: Re: [Coq-Club] non-automatic type class resolution
Date: Thu, 1 Sep 2016 22:07:05 -0400
Authentication-results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=jonikelee AT gmail.com; spf=Pass smtp.mailfrom=jonikelee AT gmail.com; spf=None smtp.helo=postmaster AT mail-qk0-f181.google.com
Ironport-phdr: 9a23:/bK+ihan1JG79dYym6n7fyz/LSx+4OfEezUN459isYplN5qZpsu+bnLW6fgltlLVR4KTs6sC0LuP9f26EjFRqdbZ6TZZL8wKD0dEwewt3CUeQ+e9QXXhK/DrayFoVO9jb3RCu0+BDE5OBczlbEfTqHDhpRQbGxH4KBYnbr+tQt2a3IyL0LW5/ISWaAFVjhK8Z6lzJVO4t1b/rM4T1KllLK8tyhLP6l9Fevpbw38gcVCUmRf/68O98bZs9i1Rv7Qq8MsWAvayRLgxUbENVGduCGsy/sC+7RQ=

On 09/01/2016 09:57 PM, Vadim Zaliva wrote:

...
In more complex cases, where one have several type class instance evars,
dependent on each other I suspect using this approach could become unwieldy.

I agree. Cases like this have been discussed before both on Coq-club and coqdev. It would be nice to have a way to selectively turn off typeclass resolution on a hole-by-hole basis with some convenient syntax.

-- Jonathan

[Coq-Club] non-automatic type class resolution, Vadim Zaliva, 09/02/2016
- Re: [Coq-Club] non-automatic type class resolution, Jonathan Leivent, 09/02/2016
  - Re: [Coq-Club] non-automatic type class resolution, Jonathan Leivent, 09/02/2016
  - Re: [Coq-Club] non-automatic type class resolution, Vadim Zaliva, 09/02/2016
    - Re: [Coq-Club] non-automatic type class resolution, Jonathan Leivent, 09/02/2016
      - Re: [Coq-Club] non-automatic type class resolution, Jonathan Leivent, 09/02/2016