caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jun.Furuse@inria.fr
To: Chris Hecker <checker@d6.com>
Cc: Pierre Weis <pierre.weis@inria.fr>,
	Oleg Trott <oleg_trott@columbia.edu>,
	John Max Skaller <skaller@ozemail.com.au>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: easy print and read (was: [Caml-list] Why are arithmetic  functions not polymorph?)
Date: Mon, 09 Jun 2003 11:40:57 +0200	[thread overview]
Message-ID: <lwadcrvb9y.wl@inria.fr> (raw)
In-Reply-To: <4.3.2.7.2.20030608014051.03139b88@localhost>

Hello,

At Sun, 08 Jun 2003 01:49:21 -0700,
Chris Hecker wrote:
> 
> >All this hard work needed a long time to mature (1995 -> 2003!) and is
> >now in a stable and satisfying state.
> 
> This is great.  My concern about generics in ocaml is one of efficiency.  I 
> read the paper (as much as I could understand), and the flow array stuff 
> seems smart and better than type pattern matching in the case where you 
> don't know the definition of the generic function at the call point, but is 
> there going to be inlining with generics as well in this initial 
> implementation? 

This is one of the TODO items of G'Caml. 
You can hope that inlining of very simple generic values such as plus
will be available in near future, (but not in the next release, sorry.)
The inlining will occur only when:

  * The type of a generic value instance is statically known.
  * The corresponding overloaded definition is an identifier, such as
	(+) and (+.)

Inlining more complex generic values such as double 
(let double x = plus x x) will be another story...

--
Jun

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      reply	other threads:[~2003-06-09  9:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 22:31 [Caml-list] Why are arithmetic functions not polymorph? hermanns
2003-05-22 23:10 ` Brian Hurt
2003-05-23  1:34 ` Nicolas Cannasse
2003-05-23  9:56 ` David Monniaux
2003-05-23 10:13   ` Ville-Pertti Keinonen
2003-05-23 16:34   ` brogoff
2003-05-23 18:02     ` Brian Hurt
2003-05-23 18:12       ` Matt Gushee
2003-05-23 20:25       ` brogoff
2003-05-23 21:15         ` Brian Hurt
2003-05-23 21:23           ` brogoff
2003-06-03  3:42         ` John Max Skaller
2003-06-03  4:10           ` Oleg Trott
2003-06-03  6:57             ` John Max Skaller
2003-06-03  3:25       ` John Max Skaller
2003-06-06  7:08         ` easy print and read (was: [Caml-list] Why are arithmetic functions not polymorph?) Oleg Trott
2003-06-06 10:46           ` Pierre Weis
2003-06-06 16:40             ` brogoff
2003-06-07 10:59               ` Stefano Zacchiroli
2003-06-07 14:44               ` Jun.Furuse
2003-06-08  6:32                 ` brogoff
2003-06-08  8:49             ` Chris Hecker
2003-06-09  9:40               ` Jun.Furuse [this message]

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=lwadcrvb9y.wl@inria.fr \
    --to=jun.furuse@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=checker@d6.com \
    --cc=oleg_trott@columbia.edu \
    --cc=pierre.weis@inria.fr \
    --cc=skaller@ozemail.com.au \
    /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).