DIP 1019--Named Arguments Lite--Community Review Round 1

[SimonN]

On Saturday, 16 February 2019 at 23:56:45 UTC, Vladimir Panteleev 
wrote:
> @named is not the best idea.

I discourage @named, too.

The lesser evil is when implementors break call sites whenever 
implementors rename their arguments. It's rare that this happens 
purely for style. (If the renaming is caused by a semantic change 
in the function, then we want noisy breakage in the call sites 
anyway, with or without @named.)

Function designers are already annotating everything with 
@property const @safe pure nothrow @nogc. Let's not bloat the 
definition even more with @named.

Besides @named, I'm happy with the proposal. Expressiveness and 
automatic checks are good.

-- Simon