Skip to Content.
Sympa Menu

coq-club - Re: [Coq-Club] Eval compute and type classes

coq-club AT inria.fr

Subject: The Coq mailing list

List archive

Re: [Coq-Club] Eval compute and type classes


Chronological Thread 
  • From: Arnaud Spiwack <aspiwack AT lix.polytechnique.fr>
  • To: Julien Tesson <julien.tesson AT univ-orleans.fr>
  • Cc: coq-club AT inria.fr
  • Subject: Re: [Coq-Club] Eval compute and type classes
  • Date: Thu, 11 Oct 2012 10:47:24 +0200

Yes.

It's occasionally useful to be able to compute with existential variables.

Why is it strange ?

On 10 October 2012 23:28, Julien Tesson <julien.tesson AT univ-orleans.fr> wrote:
Hi list,
we found a very strange "feature" of Coq 8.4 when it comes to evaluate a term which relies on type classes, here is a very small example.


Class A :={a : Type}.
Eval compute in a.


Here, [a] evaluate to  [let (a) := ?3 in a : Type]
whereas in a previous version of Coq (actually 8.3pl3) it fails with message  "Cannot infer the implicit parameter A of a",  as expected.

If we try to assign the result,
Definition x := Eval compute in a.
it fails, that's why I did'nt call this behaviour a bug, but a (very) strange feature.

we were wondering if this behaviour was known and done on purpose ?

Regards,
Julien




Archive powered by MHonArc 2.6.18.

Top of Page