From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] log function without evaluate arguments
Date: Wed, 7 Nov 2007 15:00:16 +1100 [thread overview]
Message-ID: <20071107150016.61b256ac.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <4a051d930711061939p621c0a8ao4472a82973dcc855@mail.gmail.com>
Christopher L Conway wrote:
> On 11/6/07, Brian Hurt <bhurt@janestcapital.com> wrote:
> > Also, creating a lazy thunk in Ocaml is expensive (like 140+ clock cycles),
> > while passing an argument into a function is cheap- and the common case will
> > be that the argument won't need to be evaluated, just passed in.
>
> What does this mean? Did OCaml become non-strict while I wasn't looking?
Ocaml is strict by default and optionally lazy.
The code being discussed was this:
log (lazy (Printf.printf "%s" (awfully_long_computation ())))
where everything inside
(lazy X)
is lazy evaluated.
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
"I'd rather not work with people who aren't careful. It's darwinism
in software development." -- Linus Torvalds on the linux-kernel list
next prev parent reply other threads:[~2007-11-07 4:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 17:05 tmp123
2007-11-06 16:57 ` Sylvain Le Gall
2007-11-06 18:25 ` [Caml-list] " Nicolas Pouillard
2007-11-06 18:40 ` Till Varoquaux
2007-11-06 18:49 ` Brian Hurt
2007-11-07 3:39 ` Christopher L Conway
2007-11-07 4:00 ` Erik de Castro Lopo [this message]
2007-11-07 4:10 ` Christopher L Conway
2007-11-07 13:42 ` Brian Hurt
2007-11-07 10:21 ` Nicolas Pouillard
2007-11-07 3:40 ` Christopher L Conway
[not found] ` <4a051d930711061938u25836a85ud28c610312e5896f@mail.gmail.com>
2007-11-07 10:31 ` tmp123
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=20071107150016.61b256ac.mle+ocaml@mega-nerd.com \
--to=mle+ocaml@mega-nerd.com \
--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