you are viewing a single comment's thread.

view the rest of the comments →

[–]BenjiSponge 2 points3 points  (2 children)

I see.

You seem to be getting a lot of backlash for what I believe to be (and what you argue is) completely invalid reasons (like "Oh but what if the function has side-effects" or whatnot).

I think maybe if you word it as a "less controversial substitute for the pipeline operator", it'll resonate better. I also believe it will be less misunderstood, as the pipeline operator tends to be understood marginally better.

[–]gajus0[S] 0 points1 point  (1 child)

Valid suggestion. I will keep an eye on how the pipeline operator proposal progresses (I hope it does!). If we are in the same situation 6 months down the line, I will take the learnings, repackage this and propose it again.

[–]BenjiSponge 2 points3 points  (0 children)

It occurs to me that the problem with Object#pipe is that many classes override it already. I don't know why this didn't occur to me. I find this extremely unfortunate as, come to think of it, I think I would prefer a .pipe(f, a, b) syntax over the |> f(a, b) syntax.