On Thursday, 10 September 2015 at 18:05:43 UTC, anonymous wrote:
On Thursday, 10 September 2015 at 17:55:06 UTC, Prudence wrote:
Of course, this hides the names outside the lambda, but a
warning could be issued(no different than if one does it
explicitly.
This makes the parameter names part of the API. The author of a
library is unable to rename parameter without breaking user
code. I do not believe the benefit is large enough to accept
such a drawback.
That's one of the main reasons that I hate the idea of named
arguments. It's more stuff that's part of the API, more public
stuff that you have to name correctly and risk bikeshedding
arguments over, and more stuff that can you can't change without
breaking existing code.
- Jonathan M Davis
