preparing for named arguments

[matheus]

On Monday, 26 August 2019 at 23:46:51 UTC, Jonathan M Davis wrote:
> This is exactly one of the reasons why I think that named 
> arguments are a terrible idea. Now, we get to bikeshed about 
> what the "official" name is that we should be naming all of 
> these range parameters in order to be consistent and how we 
> should deal with naming them when there are multiple range 
> arguments. None of this mattered previously. As long as the 
> name was reasonable, it was irrelevant, and even then, it 
> really only mattered for documentation purposes and for making 
> the function internals reasonable to maintain.

I think that named arguments emerged long time ago because of 
Windows API. :)

Do you remember those functions calls with lots of parameters to 
fill?

But like you said I think today it's a bad design. I program in 
C# too and barely use this feature because I try to make things 
sane.

Matheus.