From: Julien Moutinho <julien.moutinho@gmail.com>
To: Christopher Kauffman <kauffman@cs.umn.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Question on polymorphic typing for curried functions
Date: Fri, 24 Aug 2007 23:04:43 +0200 [thread overview]
Message-ID: <20070824210442.GA15226@jiyu.gnu> (raw)
In-Reply-To: <46CF34DE.301@cs.umn.edu>
On Fri, Aug 24, 2007 at 02:43:26PM -0500, Christopher Kauffman wrote:
> I am looking for a bit of information on the behavior of curried functions
> wrt polymorphic arguments. For instance, in the following example, using a
> curried function seems to lose the nice polymorphism that I desire.
> [...]
> Is there a set of rules or guidelines that determine when argument types
> are specialized versus staying polymorphic?
This may be of interest to you:
http://caml.inria.fr/pub/old_caml_site/FAQ/FAQ_EXPERT-eng.html#eta_expansion
next prev parent reply other threads:[~2007-08-24 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 19:43 Christopher Kauffman
2007-08-24 20:25 ` [Caml-list] " Jon Harrop
2007-08-24 21:04 ` Julien Moutinho [this message]
2007-08-24 23:32 ` Harrison, John R
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=20070824210442.GA15226@jiyu.gnu \
--to=julien.moutinho@gmail.com \
--cc=caml-list@inria.fr \
--cc=kauffman@cs.umn.edu \
/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