From: se8ast@... Date: 2016-03-04T12:49:07+00:00 Subject: [ruby-core:74137] [Ruby trunk Feature#12141] send and __send__ Issue #12141 has been updated by Sebastian Herm. Thanks for your feedback. :-) I agree, it's a minor (cosmetic) issue. For example, Rails uses __ send __ only 17 times in its huge codebase. :-) I don't suggest removing send, but just replacing __ send __ with invoke to have a better named alias (yes, maybe for Ruby 3.0 ?) ---------------------------------------- Feature #12141: send and __send__ https://bugs.ruby-lang.org/issues/12141#change-57282 * Author: Sebastian Herm * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Hi guys ! We have this concept of sending messages to objects with Object#send, and that's fine, but often a child class defines its own send method, so that's why we have this ugly Object#__send__ hack. So, I suggest dropping Object#__send__ and aliasing Object#send to Object#invoke instead, which seems to me as a better evocative method name. Good or bad idea ? Thanks ! -- https://bugs.ruby-lang.org/ Unsubscribe: