From: "Mike Lin" <mikelin@mit.edu>
To: "Erik de Castro Lopo" <mle+ocaml@mega-nerd.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Memoization
Date: Sat, 9 Sep 2006 11:47:51 -0400 [thread overview]
Message-ID: <2a1a1a0c0609090847j23b0b83fq1ba15e21e3faf383@mail.gmail.com> (raw)
In-Reply-To: <20060909175652.93b8d71d.mle+ocaml@mega-nerd.com>
> The particular function I'm trying to memoize is a function of
> two integers. I was hoping it might be possible to write a
> memoize function that memoizes any function of a small arbitrary
> number of parameters. Thinking about it some more I'm beginning
> to this this is not possible.
It is not very costly to give multiple parameters as a tuple. I think
I remember reading that the native code compiler can do this without a
heap allocation. -Mike
next prev parent reply other threads:[~2006-09-09 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 0:33 Memoization Erik de Castro Lopo
2006-09-09 3:38 ` [Caml-list] Memoization Andrej Bauer
2006-09-09 7:56 ` Erik de Castro Lopo
2006-09-09 15:47 ` Mike Lin [this message]
2006-09-09 21:20 ` William Neumann
2006-10-06 3:22 ` Walid Taha
2006-09-30 8:49 ` Jan Kybic
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=2a1a1a0c0609090847j23b0b83fq1ba15e21e3faf383@mail.gmail.com \
--to=mikelin@mit.edu \
--cc=caml-list@inria.fr \
--cc=mle+ocaml@mega-nerd.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;
as well as URLs for NNTP newsgroup(s).