caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Magesh Kannan <magesh@ittc.ku.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Currying vs Speed
Date: Mon, 4 Nov 2002 20:49:25 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0211042019440.26138-100000@george.ittc.ku.edu> (raw)

Hi All,

Does currying one of the arguments to a function provide any run-time 
performance improvements?

In the following code fragment,

let my_func arg1 arg2 arg3 =
  let res = arg1 + arg2 + arg3 in
    res

let my_func_wrapper arg1 arg2 arg3 =
  my_func arg1 arg2 arg3

let my_func_part = my_func 5

Does the invocation (my_func_part 10 20) run any faster than
(my_func_wrapper 5 10 20)?

Thanks,
Magesh

-------------------
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:[~2002-11-05  2:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05  2:49 Magesh Kannan [this message]
2002-11-05 17:08 ` Florian Hars

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=Pine.LNX.4.21.0211042019440.26138-100000@george.ittc.ku.edu \
    --to=magesh@ittc.ku.edu \
    --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).