From: qrczak@knm.org.pl (Marcin 'Qrczak' Kowalczyk)
To: caml-list@inria.fr
Subject: Re: [Caml-list] currying...
Date: 6 Mar 2001 19:09:28 GMT [thread overview]
Message-ID: <slrn9aadf8.up2.qrczak@qrnik.zagroda> (raw)
In-Reply-To: <4.3.2.7.2.20010306093019.00e181f0@shell16.ba.best.com>
Tue, 06 Mar 2001 09:41:38 -0800, Chris Hecker <checker@d6.com> pisze:
> Now my question is, is there any way to introspect to get at the
> arity information?
You shouldn't need it. It's an implementation detail and doesn't have
to have any meaning. It should never be used to drive the semantics -
code should behave in the same way no matter how a function is built
internally.
AFAIK this internal "uncurrying" is limited to a constant (up to 5
arguments or something). Above that functions are really implemented
as functions returning functions, in groups of 5 arguments. There
might be also differences between native code and bytecode.
> Is int -> int -> int typechecked _exactly_ like int -> (int -> int)?
Yes.
--
__("< Marcin Kowalczyk * qrczak@knm.org.pl http://qrczak.ids.net.pl/
\__/
^^ SYGNATURA ZASTĘPCZA
QRCZAK
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-03-06 19:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 9:39 Chris Hecker
2001-03-06 10:22 ` Thomas Colcombet
2001-03-06 10:33 ` Bruce Hoult
2001-03-06 10:50 ` Remi VANICAT
2001-03-06 16:31 ` Xavier Leroy
2001-03-06 17:41 ` Chris Hecker
2001-03-06 18:43 ` Sven LUTHER
2001-03-06 19:09 ` Marcin 'Qrczak' Kowalczyk [this message]
2001-03-06 20:14 ` Chris Hecker
2001-03-06 21:39 ` Marcin 'Qrczak' Kowalczyk
2001-03-06 23:23 ` Chris Hecker
2001-03-06 23:45 ` Marcin 'Qrczak' Kowalczyk
2001-03-07 1:10 ` Chris Hecker
2001-03-07 8:44 ` Marcin 'Qrczak' Kowalczyk
2001-03-06 23:51 ` Chris Hecker
2001-03-06 10:16 Adam Granicz
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=slrn9aadf8.up2.qrczak@qrnik.zagroda \
--to=qrczak@knm.org.pl \
--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).