<br><br><div class="gmail_quote">On 29 August 2012 15:21, Joachim Breitner <span dir="ltr"><<a href="mailto:breitner@kit.edu" target="_blank">breitner@kit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Facundo,<br>
<br>
Am Mittwoch, den 29.08.2012, 10:26 -0300 schrieb Facundo Domínguez:<br>
<div class="im">> > upd_noupd n =<br>
> > let l = myenum' 0 n<br>
> > in last l + length l<br>
><br>
> This could be rewritten as<br>
><br>
> > upd_noupd n =<br>
> > let l n = myenum' 0 n<br>
> > in last (l n) + length (l n)<br>
><br>
> Or a special form of let could be introduced to define locally-scoped macros:<br>
><br>
> > upd_noupd n =<br>
> > let# l = myenum' 0 n<br>
> > in last l + length l<br>
><br>
> What's the strength of the {-# NOUPDATE #-} approach?<br>
<br>
</div>it does not require refactoring of the code. There is not always a<br>
parameter handy that you can use to prevent sharing, and using () for<br>
that sometimes fails due to the full-lazyness-transformation.<br>
<br>
And a locally-scoped macros would not help in this case:<br>
<br>
test g n = g (myenum' 0 n)<br>
<br>
Now you still might want to prevent the long list to be stored, but here<br>
it cannot be done just by inlining or macro expansion.<br></blockquote><div><br></div><div>Syntactically, I'd prefer something that looks more like a function. With a pragma it's difficult to see what expression it actually affects. For example, we already have the special functions "lazy" and "inline". Since avoiding updates essentially turns lazy evaluation into call-by-name you could call it "cbn". Perhaps that suggests a different use case, though, so "nonstrict", "unshared", or "nonlazy" might be more self-explanatory.</div>
<div><br></div><div>I'd also like to point out that avoiding updates can dramatically improve the kind of speedups my tracing JIT can achieve. In particular, on some benchmarks, it can optimise idiomatic Haskell code to the same level as stream fusion. I can simulate that by avoiding *all* updates (i.e., use call-by-name), but that would break some programs badly. (Technically, that's all legal, but I'm pretty sure it breaks any "tying-the-knot" tricks.)</div>
<div><br></div></div>