Hi,
Am 01.03.2009 um 02:19 schrieb Belfabius:
I quickly learned the -> macro can't be used in the same way for one
simple reason; the value that is threaded through to the forms is
always placed in the first argument position. How about adding a
macro -- it could be called |> just as in F# --
First, I have to say thanks. I'm only a part-time Clojure user, and I
didn't know of the -> macro until today. Second, I think the ->
syntax leads to more readable code for precisely those situations
where you're coding a sequence of actions. Finally, I've got a
comment about what I think might
2009/2/28 Stuart Sierra
>
> On Feb 27, 1:39 pm, "John D. Hume" wrote:
> > As a Java/Ruby guy who is not used to reading inside out, I'm curious
> > as to whether people who ARE accustomed to LISP find the -> macro
> > distracting since it flops things around. Are there circumstances
> > where yo
On Feb 27, 1:39 pm, "John D. Hume" wrote:
> As a Java/Ruby guy who is not used to reading inside out, I'm curious
> as to whether people who ARE accustomed to LISP find the -> macro
> distracting since it flops things around. Are there circumstances
> where you prefer it?
Definitely. When you'r
>
> It's pretty useful for nested keywords:
>
> (:name (:profile (:user message)))
>
> (-> message :user :profile :name)
>
> - James
That is really cool. Once again the language and the community impress
me with how elegant the language is.
Allen
--~--~-~--~~~--
On Feb 27, 6:39 pm, "John D. Hume" wrote:
> As a Java/Ruby guy who is not used to reading inside out, I'm curious
> as to whether people who ARE accustomed to LISP find the -> macro
> distracting since it flops things around. Are there circumstances
> where you prefer it?
It's pretty useful for
On Wed, Feb 25, 2009 at 4:11 PM, Jason Wolfe wrote:
> (you'll get use to reading inside-out quickly).
As a Java/Ruby guy who is not used to reading inside out, I'm curious
as to whether people who ARE accustomed to LISP find the -> macro
distracting since it flops things around. Are there circum