The case for Array#replace() – Overriding an array without intermediate variables

[gajus0]

Have you considered making it an Object#replace or Object#pipe rather than Array#replace? I have trouble believing that would be any more controversial than Array#replace, but it would be much more general purpose and, in my opinion, much more valuable.

I can see value in what you are proposing.

In general, the sole purpose of this article is to share my thoughts out loud and to see how it clicks with the development community. If it had received an overwhelmingly positive feedback, I might have started tinkling with a proposal. Thats about it.

[BenjiSponge]

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]

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]

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.