coq-club AT inria.fr
Subject: The Coq mailing list
List archive
- From: Guillaume Melquiond <guillaume.melquiond AT inria.fr>
- To: coq-club AT inria.fr
- Subject: Re: [Coq-Club] Why can't unit be a primitive record?
- Date: Sun, 17 Sep 2017 08:37:33 +0200
On 17/09/2017 03:57, Jasper Hugunin wrote:
> I don't think your primitive record example quite works; I would hope
> that when checking
> Rec (t.(p₀), ..., t.(pₙ)) ≡ u,
> u gets expanded so we have
> Rec (t.(p₀), ..., t.(pₙ)) ≡ Rec (u.(p₀), ..., u.(pₙ)).
The actual rule is even more generic: when it fails to ensure
Rec (t₀, ..., tₙ) ≡ u,
the kernel turns it into
Rec (t₀, ..., tₙ) ≡ Rec (u.(p₀), ..., u.(pₙ)).
There are no projections on the left-hand side, a priori.
Best regards,
Guillaume
- [Coq-Club] Why can't unit be a primitive record?, Jasper Hugunin, 09/16/2017
- Re: [Coq-Club] Why can't unit be a primitive record?, Pierre-Marie Pédrot, 09/16/2017
- Re: [Coq-Club] Why can't unit be a primitive record?, Jasper Hugunin, 09/17/2017
- Re: [Coq-Club] Why can't unit be a primitive record?, Guillaume Melquiond, 09/17/2017
- Re: [Coq-Club] Why can't unit be a primitive record?, Jasper Hugunin, 09/17/2017
- Re: [Coq-Club] Why can't unit be a primitive record?, Pierre-Marie Pédrot, 09/16/2017
Archive powered by MHonArc 2.6.18.