Truly is, much nicer than that lonely `_1`

I'd have thought allowing _ as a synonym for _1 would have been more aesthetically consistent. That's the path I went with when designing my CL #λ reader macro, personally.

_2 can be as bad as _1

I don't understand the point of it when the `.map(&:upcase)` syntax is shorter. This just seems like yet another syntactic sugar Rubyism that doesn't really add anything.

If it's an alternative to the `|x|` syntax when using only one block variable, then I like that.

`arr.map { it.thing.blah.stuff }`

The `&:` doesn't work in that context

Not to point any fingers, but shows that the previous commenter have not struggled with this :)

&: is very nice, but not enough.

That only works when calling a method on the things you’re iterating thru, it is a replacement for the single variable block example you gave there

Don't say that word!

https://www.youtube.com/watch?v=RZvsGdJP3ng

Does `it` conflict with Rspec's `it`? Surely they've thought of this, but to my eye it looks like it would get confusing.

Nope it doesn’t, they did take that into account during development.