caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Stephan Houben <stephan@pcrm.win.tue.nl>
To: caml-list@inria.fr
Subject: inlining functions called through functor parameters?
Date: Mon, 31 Jan 2000 10:34:47 +0100	[thread overview]
Message-ID: <20000131103447.A16550@pcrm.win.tue.nl> (raw)

Hello list,

While searching the Caml mailing list archive, I found
a message from Xavier Leroy, posted on Tue Jun 23 1998,
in which he describes the fact that:
"... it is true that functions taken from the
 functor parameter are always called via their closures".

I was wondering if this is still true (since 1998 is a long
time ago, in internet time at least), and if there are any plans
to implement more inlining for such functions.
The reason I ask is because I'm writing a couple of modules where
lots of small funtions are called via a functor parameter, and
I'm wondering if it's worth the trouble to inline them "by hand".

Greetings,

Stephan Houben




             reply	other threads:[~2000-02-02 15:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-31  9:34 Stephan Houben [this message]
2000-02-03 18:38 ` Xavier Leroy

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=20000131103447.A16550@pcrm.win.tue.nl \
    --to=stephan@pcrm.win.tue.nl \
    --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).