On 27 February 2015 at 16:13, stepharo <[email protected]> wrote:
> Are we sure that we want to use that =>
> I thought about = but this is not an assignement this is a declaration and
> normally we use | for declaration.
>
So what would be other alternatives before the world use =>
>
But | for local variables is syntax, and it's used as a bracket. It's also
the logical or operator…
I'd propose :: because it recalls the :x for block arguments, or -- because
it looks like a typographic em-dash:
slots: {
#local -- ProcessLocalSlot.
#foo -- SomeOtherKindOfSlot.
By the way, using an operator in this way is a little strange: what you
read does not match the usual precedence rules (#default: is not a factory
method of ProcessLocalSlot, it's an accessor on the result of #local =>
ProcessLocalSlot)
Then I still do not understand why we have empty classVariables: to me it
> does not make sense. I do not get why we like to have empty collections for
> the sake of having empty collections. We are trapped in some strange ways
> of thinking.
>
Are there strong arguments against a cascade ?
As far as I understand, the only real constraint is that the set of
messages that are authorized in class creation syntax should be closed in
some way.
--
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet
