Julian Rohrhuber

Ah ok, I understand it better now, thanks! Whether we whish to want this will entirely depend on the use cases, which may have to be written out.

Hm, in the latest dev branch om macOS, this doesn't crach, but throws an error: ``` e = (); e.put(\cats, \birds, otherAnimals: \dogs); e = IdentityDictionary.new; e.put(\cats, \birds, otherAnimals: \dogs);...

P.S. it is of course wrong that `e` is taken as immutable.

> [@telephon](https://github.com/telephon) [@JordanHendersonMusic](https://github.com/JordanHendersonMusic) do you think this is serious enough to warrant releasing 3.14.1 with a fix? It (https://github.com/supercollider/supercollider/issues/7156) is a breaking change (breaking code of third party that uses...

> Where the outcomes differ, they basically wouldn't have been usable before, so I'd think of it more as a bug fix than a change If you are sure that...

exactly, thats the point !!

If I understand correctly, such syntax could be generally useful? For a first step, perhaps the delegation of methods just as a normal method call with a primitive? ```supercollider doesNotUnderstand...

I see, you are proposing an alternative to inheritance. It is generally unrelated to the PR, it could be used anywhere. It is a little OT, but let's keep it...

>In terms of pattern matching - I'm JUST thinking of using the list of methods of a class to auto-generate forwarding methods. am I right to think that "pattern matching"...

@scztt Am I right that the syntax is a more compact and efficient replacement of something like this? ```supercollider Delegator : AbstractObject { var delegates, selectors; doesNotUnderstand { | selector...