Feature #14594: Rethink yield_self's name - Ruby - Ruby Issue Tracking System

I feel really uncomfortable raising the question again, but... In several months since 2.5 release I've written a lot of code with yield_self (using backports gem with earlier versions of Ruby when necessary), and explained it several times to students, and colleagues (and in this blog post which have gained pretty decent attention). I should say that I am still assured the name chosen is really n

[hiromichinomata]

"After a long consideration, I decided to pick then as an alias to yield_self."