From: Mackenzie Straight <eizneckam@gmail.com>
To: Alessandro Baretta <a.baretta@barettadeit.com>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] let rec x = lazy x
Date: Wed, 11 Jan 2006 02:55:38 -0700 [thread overview]
Message-ID: <a7af81520601110155w75362180qdca02a8a51d23593@mail.gmail.com> (raw)
In-Reply-To: <43C4D4F7.8090109@barettadeit.com>
On 1/11/06, Alessandro Baretta <a.baretta@barettadeit.com> wrote:
> Strange as it may seem, it seems to work! With -rectypes enabled of course.
>
> Obviously, forcing x does not produce anything sensible, but it does produce
> something. Am I justified in believing that the result is a long chain of
> lazy-blocks, the last one containing a Stack_overflow exception?
http://caml.inria.fr/pub/docs/manual-ocaml/libref/Lazy.html
You don't want to do this.
next prev parent reply other threads:[~2006-01-11 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 9:50 Alessandro Baretta
2006-01-11 9:55 ` Mackenzie Straight [this message]
2006-01-11 10:04 ` [Caml-list] " Alessandro Baretta
2006-01-11 10:20 ` Mackenzie Straight
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=a7af81520601110155w75362180qdca02a8a51d23593@mail.gmail.com \
--to=eizneckam@gmail.com \
--cc=a.baretta@barettadeit.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;
as well as URLs for NNTP newsgroup(s).