From: Zheng Li <li@pps.jussieu.fr>
To: caml-list@inria.fr
Subject: Re: Help me find this pdf
Date: Fri, 19 Oct 2007 16:41:02 +0200 [thread overview]
Message-ID: <87myuf2mm9.fsf@pps.jussieu.fr> (raw)
In-Reply-To: <6f9f8f4a0710190649x2ad33e26h3b1421a63df21780@mail.gmail.com>
Just for fun :>
----
# let rec f ?(pred=[]) s =
let conv = function [] -> [<>] | l -> [<'Some l>] in
[< match s with parser
| [<'Some x>] -> f ~pred:(pred@x) s
| [<'h>] -> [<conv pred; 'h; f s>]
| [<>] -> [<conv pred>] >];;
# open Sdflow;;
# of_list [Some[1]; Some[2; 3]; None; Some[4; 5]] |> f |> to_list;;
- : int list option list = [Some [1; 2; 3]; None; Some [4; 5]]
----
Note that any first element's evaluation is also lazy.
The [f] above is defined with plain Stream, but you can archive the same with
SDFlow's high-order combinator here such as map, map_fold etc.
"Loup Vaillant" <loup.vaillant@gmail.com> writes:
> If we really want to, we can delay the evaluation at all costs, by
> delaying even the car of the Cons cells
>
> type 'a node_t =
> | Empty
> | Cons of 'a Lazy.t * 'a lazylist
> and 'a lazylist = 'a node_t Lazy.t
> ;;
>
> For instance, when figuring out if the list is empty or not, the first
> element isn't forced. You can even force the second element of the
> list without forcing the first:
>
> match Lazy.force zlst with
> | Cons(_, tl) ->
> match Lazy.force tl with
> | Cons(hd, _) ->
> let head = Lazy.force hd in
> [...]
> ;;
>
> Or, assuming I can get away with unsafe code:
>
> let hd zlst = match Lazy.force zlst with
> | Cons(h, _) = h
> ;;
> let tl zlst = match Lazy.force zlst with
> | Cons(_, t) = t
> ;;
>
> (* and finally *)
> match Lazy.force hd (tl zlst)
> with [...]
> ;;
--
Zheng Li
http://www.pps.jussieu.fr/~li
next prev parent reply other threads:[~2007-10-19 14:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 9:52 Tom
2007-10-18 10:33 ` [Caml-list] " skaller
2007-10-18 11:01 ` Andreas Rossberg
2007-10-18 12:25 ` Jon Harrop
2007-10-18 12:40 ` Arnaud Spiwack
2007-10-18 13:17 ` Jon Harrop
2007-10-18 15:15 ` Till Varoquaux
2007-10-18 12:46 ` Jacques Garrigue
2007-10-18 13:57 ` Jon Harrop
2007-10-18 14:22 ` Brian Hurt
2007-10-18 14:52 ` Robert Fischer
2007-10-18 15:04 ` Eric Cooper
2007-10-18 17:18 ` Jon Harrop
2007-10-19 1:16 ` skaller
2007-10-19 5:09 ` Bárður Árantsson
2007-10-19 5:23 ` [Caml-list] " Erik de Castro Lopo
2007-10-19 5:46 ` Bárður Árantsson
2007-10-19 12:25 ` [Caml-list] " Christophe Raffalli
2007-10-19 12:47 ` Luc Maranget
2007-10-20 14:26 ` Christophe Raffalli
2007-10-19 14:48 ` Robert Fischer
2007-10-19 21:43 ` Andreas Rossberg
2007-10-19 21:51 ` Robert Fischer
2007-10-20 13:10 ` Andreas Rossberg
2007-10-19 23:10 ` Jon Harrop
2007-10-20 1:13 ` skaller
2007-10-20 6:36 ` Tom
2007-10-21 11:17 ` skaller
2007-10-19 8:55 ` Zheng Li
2007-10-19 22:27 ` [Caml-list] " Jon Harrop
2007-10-19 13:00 ` [Caml-list] " Brian Hurt
2007-10-19 13:49 ` Loup Vaillant
2007-10-19 14:41 ` Zheng Li [this message]
2007-10-19 23:09 ` Jon Harrop
2007-10-18 20:07 ` Tom
2007-10-19 0:59 ` skaller
2007-10-18 20:48 ` Lauri Alanko
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=87myuf2mm9.fsf@pps.jussieu.fr \
--to=li@pps.jussieu.fr \
--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