$. is kind of the worst of all possible worlds to me. <div><br></div><div>(|>) at least has the ML precedent going for it, but ($.) using the . to indicate the side that the function is on offers very little to visually distinguish it from ($) and no such precedent to motivate it.<div>
<br></div><div>The first time I read your post I read the . as the end of sentence marker. =P</div><div><br></div><div>-Edward<br><br><div class="gmail_quote">On Tue, Nov 20, 2012 at 4:08 PM, Gábor Lehel <span dir="ltr"><<a href="mailto:illissius@gmail.com" target="_blank">illissius@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Another option that was raised in a mailing list thread at some point<br>
(I think it was one about records): $.<br>
<br>
The idea being to evoke the dot operator of object-oriented languages<br>
together with the existing ($) of function application.<br>
<br>
theList $. filter even $. map (*2) $. sum<br>
<br>
If you read it by focusing on the dots as in an OO language it sort of<br>
works. Not sure how I feel about it, throwing it out there. As a<br>
candidate for the least bad choice I think it at least qualifies.<br>
<div class="HOEnZb"><div class="h5"><br>
On Tue, Nov 20, 2012 at 5:59 PM, Yitzchak Gale <<a href="mailto:gale@sefer.org">gale@sefer.org</a>> wrote:<br>
> It is a common idiom to write a sequence of composed combinators in<br>
> reverse order to the way they would be written with ($) or (.). That<br>
> naturally expresses the idea of the combinators as operations being<br>
> applied in the given order.<br>
><br>
> This comes up so often, and is commonly used so many times in a single<br>
> expression, that Control.Arrow.>>> is far too wordy, and even a two-<br>
> character operator is awkward.<br>
><br>
> Surprisingly, until recently the operator (&) was still not used in any<br>
> of the popular libraries, and its name naturally expresses the idea we are<br>
> looking for. This operator has now been defined in the lens package. We<br>
> hereby propose to move it to its natural home for more general use,<br>
> Data.Function.<br>
><br>
> As in the lens package, we define the operator as a flipped version of<br>
> ($), but with slightly higher precedence for better interaction with<br>
> ($), and with left associativity. This definition has already proven<br>
> useful and convenient even in the presence of the large and varied corpus<br>
> of combinators and operators in the lens package. (There it was formerly<br>
> known as (%), but that clashed with the usual meaning of (%) from<br>
> Data.Ratio.)<br>
><br>
> infixl 1 &<br>
> (&) :: a -> (a -> b) -> b<br>
> a & f = f a<br>
> {-# INLINE (&) #-}<br>
><br>
> Discussion period: 2 weeks<br>
><br>
> <a href="http://hackage.haskell.org/trac/ghc/ticket/7434" target="_blank">http://hackage.haskell.org/trac/ghc/ticket/7434</a><br>
><br>
> Thanks,<br>
> Yitz<br>
><br>
</div></div><div class="im HOEnZb">> _______________________________________________<br>
> Libraries mailing list<br>
> <a href="mailto:Libraries@haskell.org">Libraries@haskell.org</a><br>
> <a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
><br>
<br>
<br>
<br>
</div><div class="im HOEnZb">--<br>
Your ship was destroyed in a monadic eruption.<br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Libraries mailing list<br>
<a href="mailto:Libraries@haskell.org">Libraries@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
</div></div></blockquote></div><br></div></div>