From: Peng Zang <peng.zang@gmail.com>
To: caml-list@yquem.inria.fr
Cc: "Charles Hymans" <charles.hymans@gmail.com>
Subject: Re: [Caml-list] optimization of sequence of List.map and inlining
Date: Tue, 10 Jun 2008 18:10:03 -0400 [thread overview]
Message-ID: <200806101810.06553.peng.zang@gmail.com> (raw)
In-Reply-To: <676aba050806101201x526f03b1lf1fdbed665ee2e3f@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ExtLib has an Enum module. It has lazy maps among other things. This means I
can perform multiple maps and it will not create intermediate data
structures. Example (++ is function composition and $ is function
application):
Enum.fold (+) 0
++ Enum.map (( * ) 2)
++ Enum.map ((+) 1)
$ List.enum [1;2;3;4;5]
Will add one to everything in the list, double it and then sum the list, which
yields 40.
Peng
On Tuesday 10 June 2008 03:01:12 pm Charles Hymans wrote:
> Let's say, I have the following code:
>
> let f l = List.map succ l
>
> ....
>
> let l = f l in
> let l = List.map succ l in
> do_something_with l
>
>
> Is there a way to tell the compiler to optimize it so that it runs as fast
> as this code:
> let l = List.map (fun x -> succ (succ x)) l in
> l
> In the first case, there are two passes where succ is applied to each
> elements of the list.
> In the second case, there is only one pass that applies succ twice to each
> element of the list.
>
> Thank you,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFITvu+fIRcEFL/JewRAqmMAJ9rWadpHtt2ZiE8EDn4iIKoASDPegCgi0mM
p8iIohGVfxAXXOboMiiNKI4=
=XALu
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-06-10 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:01 Charles Hymans
2008-06-10 19:21 ` [Caml-list] " Jon Harrop
2008-06-10 20:55 ` Richard Jones
2008-06-10 22:10 ` Peng Zang [this message]
2008-06-10 23:07 ` Brian Hurt
2008-06-17 14:36 ` Jon Harrop
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=200806101810.06553.peng.zang@gmail.com \
--to=peng.zang@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=charles.hymans@gmail.com \
/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