send and __send__
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
So, I suggest dropping
Object#__send__ and aliasing
Object#invoke instead, which seems to me as a better evocative method name.
Good or bad idea ?
#3 [ruby-core:74127] Updated by shevegen (Robert A. Heiler) over 1 year ago
I think this could only be done in ruby 3.x
But I believe that
.send will remain because it is super short. :)
In the later ruby days, people added
.send is still so
much shorter to use and write;
.invoke would also be longer to type. :D
The statement that classes often define their own
.send is not true though.
I think for 5000 ruby classes that I may have written so far in 12 years
or so, I could not recall any more instance than one or two at max where
I would need a custom
__send__ - it seems very specialized
and thus I don't think this warrants a change of the name
.send() - but
that is of course just my own personal opinion here.
#5 [ruby-core:74137] Updated by hermes128 (Sebastian Herm) over 1 year ago
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
invoke to have a better named alias (yes, maybe for Ruby 3.0 ?)
#7 [ruby-core:74139] Updated by mame (Yusuke Endoh) over 1 year ago
I can't understand this issue. You know there is
send is often overridden. Then, why do you think
invoke is okay? We can easily find a lot of cases that
invoke is defined.
Yusuke Endoh email@example.com
#9 [ruby-core:74291] Updated by jwmittag (Jörg W Mittag) over 1 year ago
Martin Dürst wrote:
I agree with Yusuke. The name
__send__is chosen explicitly to show that this is an 'internal' method with special status.
Also, the messaging metaphor is at the core of Smalltalk-style OOP. And the very heart of this metaphor is precisely that you do not "call" or "invoke" methods, but rather send messages to objects which then may or may not invoke a method for you in response to that message, and that method may or may not have the same name as the message. Or, they may forward the message to somewhere else. Or, they may ignore the message.