From: Jake Donham <jake@donham.org>
To: Warren Harris <warrensomebody@gmail.com>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] lazy vs fun
Date: Mon, 24 Aug 2009 15:18:33 -0700 [thread overview]
Message-ID: <c7e4e9f0908241518r71f2d27bv53ec64a2156fe61a@mail.gmail.com> (raw)
In-Reply-To: <F950E129-5A1A-46A1-A85C-90A8CCAE03A5@gmail.com>
On Mon, Aug 24, 2009 at 3:15 PM, Warren Harris<warrensomebody@gmail.com> wrote:
>> Lazy cells don't just defer, they also memoize the returned value once
>> the cell is forced.
>
> Thanks Jake - I guess I overlooked that in the manual.
Hope you're doing well. Best of luck on the CUFP talk.
Jake
next prev parent reply other threads:[~2009-08-24 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 21:57 Warren Harris
2009-08-24 22:04 ` [Caml-list] " Jake Donham
2009-08-24 22:15 ` Warren Harris
2009-08-24 22:18 ` Jake Donham [this message]
2009-08-24 22:06 ` Stéphane Glondu
2009-08-24 22:19 ` Martin Jambon
2009-08-24 23:11 ` Martin Jambon
2009-08-24 23:33 ` Warren Harris
2009-08-25 5:19 ` rixed
2009-08-25 6:29 ` David Allsopp
2009-08-25 18:09 ` rixed
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=c7e4e9f0908241518r71f2d27bv53ec64a2156fe61a@mail.gmail.com \
--to=jake@donham.org \
--cc=caml-list@inria.fr \
--cc=warrensomebody@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;
as well as URLs for NNTP newsgroup(s).