From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Roberto Di Cosmo <roberto@dicosmo.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: GADT examples: composable functions list (Was: Re: [Caml-list] Wanted: GADT examples: string length, counting module x)
Date: Thu, 22 Mar 2012 10:46:33 +0100 [thread overview]
Message-ID: <062C697B60F0423CBF94220A63C44633@erratique.ch> (raw)
In-Reply-To: <20120322092806.GA29219@voyager>
Le jeudi, 22 mars 2012 à 10:28, Roberto Di Cosmo a écrit :
> Without GADT
> ------------
>
> One can get away cheating the type system and declaring the type
You don't need to cheat the type system with Obj without GADT.
http://caml.inria.fr/pub/ml-archives/caml-list/2004/01/52732867110697f55650778d883ae5e9.en.html
Not to say that it's not involved, but it's possible.
Best,
Daniel
next prev parent reply other threads:[~2012-03-22 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 9:28 Roberto Di Cosmo
2012-03-22 9:46 ` Daniel Bünzli [this message]
2012-03-22 10:54 ` Roberto Di Cosmo
2012-03-22 14:31 ` Markus Mottl
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=062C697B60F0423CBF94220A63C44633@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@yquem.inria.fr \
--cc=roberto@dicosmo.org \
/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).