Back in the time of ModularSmalltalk and S#, we had fierce discussions on a
symbol resolution to implement selector namespaces. We had something like that:
Symbol + Namespace = selector
As a result, several namespaces could define a method with the same selector on
a same class, thus avoiding c
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
really wanted:
Selector
UnarySele
