All of this, and: what happens when a client compiles against a given
named method signature, and then, through separate compilation, the
method signature changes, say, to add a new parameter? Dealing with
this in some form seems essential, as, the most common cases where you
want to invoke
My note on named parameters:
Supporting real named parameters that works with overriding and backward
compatibility is hard, but i believe there is a sweet spot.
- a method can declare to support named parameters by using a new modifier
'named'.
so - all parameters are named or none are, you
> On Nov 30, 2017, at 1:29 PM, Brian Goetz wrote:
> . . .
> So, while named parameters are a reasonable feature to explore, trying to
> staple them onto data classes would be a mistake. They are their own
> feature. We're open to exploring it, but we've got our plate