From: mame@... Date: 2016-03-04T13:42:03+00:00 Subject: [ruby-core:74139] [Ruby trunk Feature#12141] send and __send__ Issue #12141 has been updated by Yusuke Endoh. I can't understand this issue. You know there is `__send__` because `send` is often overridden. Then, why do you think `invoke` is okay? We can easily find a lot of cases that `invoke` is defined. https://github.com/ruby/rake/blob/78d81799ad0b440478f6a99ff9af36ea131bda90/lib/rake/task.rb#L171 https://github.com/search?l=ruby&q=%22def+invoke%22&ref=searchresults&type=Code&utf8=%E2%9C%93 -- Yusuke Endoh ---------------------------------------- Feature #12141: send and __send__ https://bugs.ruby-lang.org/issues/12141#change-57284 * 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: