You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Again, just like named arguments, named type arguments do not need to be in the same order that they are declared, as long as all non-default type parameters are specified.
voidF<T,U,V= C>(){}F<U: A,T: B>();
It will be possible to mix positional and named type arguments,
This discussion was converted from issue #280 on September 08, 2020 19:44.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Named type arguments
Proposal: dotnet/roslyn#6207
Named type arguments are useful for various use cases:
Again, just like named arguments, named type arguments do not need to be in the same order that they are declared, as long as all non-default type parameters are specified.
It will be possible to mix positional and named type arguments,
Beta Was this translation helpful? Give feedback.
All reactions