Igor Stasenko wrote
> Symbol + ??? => Selector
>
> give me a strong reason.
>
> i like the idea of shrinking a Symbol's protocol and putting it into
> lean and clean place - Symbol.
While fixing Issue 15523: "Code Cruft Rule Only Matches One-Liners", I
reeeeeally wanted:
Selector
UnarySelector
BinarySelector
KeywordSelector
so that I could double dispatch. It made me remember this old interesting
thread. So, in addition to the conceptual clarity reification would provide,
this provided a clear (to me) case of technical benefit. We could eliminate
the ~20 or so senders of isUnary, ~20 of isBinary, and ~20 isKeyword in the
Kernel for a start...
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/funny-idea-Symbol-vs-Selector-tp2335774p4826193.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
