coq-club AT inria.fr
Subject: The Coq mailing list
List archive
- From: Adam Chlipala <adamc AT hcoop.net>
- To: "Kouskoulas, Yanni A." <Yanni.Kouskoulas AT jhuapl.edu>
- Cc: "coq-club AT pauillac.inria.fr" <coq-club AT pauillac.inria.fr>
- Subject: Re: [Coq-Club] available context in refine 'holes'
- Date: Sun, 11 Jan 2009 11:54:34 -0500
- List-archive: <http://pauillac.inria.fr/pipermail/coq-club/>
Kouskoulas, Yanni A. wrote:
I find that when using refine, the context that I have access to lacks
assumptions that I think should be available.
[refine] operates with a literal treatment of the CIC typing rules. You can see from the CIC section of the manual that no assumptions relating discriminees and pattern variables are added for you; you need to use the dependent [match] annotations to get those, and there is no annotation pattern that always brings you the extra assumptions you expect without altering the "computational part" of your match. This can seem a baffling design decision at first, but a completely general mechanism would need to solve undecidable problems.
So, you have a few options:
- Use tactics, like you're already doing (not so nice)
- Learn about and apply dependent [match] annotations (The only source I'm aware of for tips of the trade on this subject is the [still incomplete!] textbook I'm writing: http://adam.chlipala.net/cpdt/)
- Use Program or some other convenience layer built on top of CIC
- [Coq-Club] available context in refine 'holes', Kouskoulas, Yanni A.
- [Coq-Club] RE: available context in refine 'holes', Kouskoulas, Yanni A.
- Re: [Coq-Club] available context in refine 'holes', Adam Chlipala
- RE: [Coq-Club] available context in refine 'holes', Kouskoulas, Yanni A.
Archive powered by MhonArc 2.6.16.