C# 7.x: non-trailing named args #216
Conversation
|
Converting to draft until we're ready for C# 7 |
BillWagner
force-pushed
the
Rex-v7-nontrailing-named-args
branch
from
acda4ac to
6e2316f
Compare
|
@RexJaeschke I think this is ready. I'll remove the draft status so it's in my queue to review. |
BillWagner
force-pushed
the
Rex-v7-nontrailing-named-args
branch
from
5423185 to
e187785
Compare
jskeet
added
Review: complete
There was a problem hiding this comment.
It is short and clear, though I wonder why it was added [*] I think we can approve it.
Oh, and I think we should stick with "following"
[*] It doesn't seem to add much of benefit. It would have made more sense to me if M(b: false, cValue) was supported, i.e. accept the defaults before b and give values for b onwards.
I've definitely found it useful in real code. It's not that unusual to have a set of arguments that are already in positional order, but you want to clarify two arguments of the same type, without specifying the names of all the arguments from there onwards. |
Co-authored-by: Bill Wagner <wiwagn@microsoft.com>
|
closing and reopening |
The standard committe has merged the updates to the standard for the following features: - dotnet/csharpstandard#216 - non-trailing named arguments - dotnet/csharpstandard#236 - default literals Remove the feature speclets from the publishing list, and fix any related links.
* remove feature specs The standard committe has merged the updates to the standard for the following features: - dotnet/csharpstandard#216 - non-trailing named arguments - dotnet/csharpstandard#236 - default literals Remove the feature speclets from the publishing list, and fix any related links. * add redirections Add the redirections for removed proposal specs. * fix typo
No description provided.