From: Paolo Herms <paolo.herms@cea.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] type constructor polymorphism
Date: Fri, 25 Feb 2011 11:12:55 +0100 [thread overview]
Message-ID: <201102251112.56387.paolo.herms@cea.fr> (raw)
In-Reply-To: <1962615140.235442.1298625990054.JavaMail.root@zmbs3.inria.fr>
On Friday 25 February 2011 10:26:30 Damien Pous wrote:
> How would you translate the following (pseudo)Coq code ?
> [...]
using
Recursive Extraction map_one map_two map_many.
Seriously, why not have Coq extracted parts of your library? It may use some
magic here and there but you can be sure it's what you wanted.
You just have to make sure you don't call functions like your k directly from
caml code but through Coq extracted wrappers whose types are also in ml,
like your map functions.
--
Paolo Herms
PhD Student - CEA-LIST Software Safety Lab. / INRIA ProVal Project
Paris, France
next parent reply other threads:[~2011-02-25 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1962615140.235442.1298625990054.JavaMail.root@zmbs3.inria.fr>
2011-02-25 10:12 ` Paolo Herms [this message]
2011-02-25 9:26 Damien Pous
2011-02-25 9:47 ` Gabriel Scherer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201102251112.56387.paolo.herms@cea.fr \
--to=paolo.herms@cea.fr \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).