From: "sebastien FURIC" <sebastien.furic@tni-valiosys.com>
To: sebastien FURIC <sebastien.furic@tni-valiosys.com>
Cc: SooHyoung Oh <shoh@duonix.com>, OCaml Mailing list <caml-list@inria.fr>
Subject: Re: [Caml-list] fib with lazy list
Date: Wed, 23 Apr 2003 14:24:10 +0200 [thread overview]
Message-ID: <3EA685EA.9AA4DF93@tni.fr> (raw)
In-Reply-To: <3EA6827C.64D3D22@tni.fr>
Sorry, a typo:
sebastien FURIC a écrit :
>
> The following code solves your problem:
>
> type 'a llist = LList of 'a * 'a llist Lazy.t | Empty
>
> let tl = function
> | Empty -> failwith "tl: empty list"
> | LList (_, xs) -> xs
^^^^^^^^^^^^^^^^^^^^^
| LList (_, lxs) -> Lazy.force lxs
Cheers,
Sebastien.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-04-23 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 10:53 SooHyoung Oh
2003-04-23 12:09 ` sebastien FURIC
2003-04-23 12:24 ` sebastien FURIC [this message]
2003-04-23 12:20 ` Michel Quercia
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=3EA685EA.9AA4DF93@tni.fr \
--to=sebastien.furic@tni-valiosys.com \
--cc=caml-list@inria.fr \
--cc=shoh@duonix.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).