From: Tom <tom.primozic@gmail.com>
To: "Jon Harrop" <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Help me find this pdf
Date: Thu, 18 Oct 2007 22:07:08 +0200 [thread overview]
Message-ID: <c1490a380710181307q547fe923xc73c99be2a5f6533@mail.gmail.com> (raw)
In-Reply-To: <200710181325.30668.jon@ffconsultancy.com>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
On 18/10/2007, Andreas Rossberg <rossberg@mpi-sws.mpg.de> wrote:
>
>
> I guess you mean this one:
>
> http://web.cecs.pdx.edu/~sheard/papers/ExplicitLazy.ps
>
> The primitive you're alluding to is called "mimic" in it.
Exactly! Thanks! I owe my (future) success to you :)
On 18/10/2007, skaller <skaller@users.sourceforge.net> wrote:
>
>
> No, but Felix does it by default
>
What do you mean? You mean that if I write a map
map f [] = []
map f x:xs = f x : map f xs
I can apply it both to infinite and lazy lists?
nums n = n : nums (n + 1)
map (+1) (nums 4)
map (print_int) [1; 5; 6]
On 18/10/2007, Jon Harrop <jon@ffconsultancy.com> wrote:
>
>
> Scala can do something similar by controlling evaluation simply by
> altering
> the signature. However, I've reviewed Haskell recently and I think
> complete
> laziness is more of a hindrance than a benefit. The only think I'd like to
> see added to eager FPLs is the ability to pattern match over lazy values,
> forcing them only when necessary.
>
I never said anything about complete laziness. Actually, I positively agree
with you, and I was searching for this paper as I don't want complete
laziness. However, I consider laziness very useful in particular situations!
For example, see this comment:
http://programming.reddit.com/info/2mxh4/comments/c2ngwb
- Tom
[-- Attachment #2: Type: text/html, Size: 2464 bytes --]
next prev parent reply other threads:[~2007-10-18 20:07 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
2007-10-19 23:09 ` [Caml-list] " Jon Harrop
2007-10-18 20:07 ` Tom [this message]
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=c1490a380710181307q547fe923xc73c99be2a5f6533@mail.gmail.com \
--to=tom.primozic@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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