No, you can't. The ValueTuple
types are actually independent of the named field support in C#. The latter works more like named properties for anonymous types. That is, the compiler analyzes the code and generates aliases to the appropriate members according to your declarations and usages. It is through the assignment that the compiler learns the names of the fields. Since the basic constructor syntax doesn't provide a mechanism to name the fields, you can't use that to directly generate a tuple with named fields.
Of course, there are ways you can re-interpret the value returned from the constructor syntax, to assign names to that returned value. I'm assuming you're aware of that approach and are looking for something more direct.
As an example of what I mean by "re-interpret", you could do something like this:
static (int value, string text) ConvertToNamed((int, string) t) => t;
then this would name the fields, in a new variable:
var t1 = new ValueTuple<int, string>(21, "hello");
var t2 = ConvertToNamed(t1);
The variable t1
is stuck with Item1
and Item2
. But the compiler will implicitly generate the desired names for the variable t2
.
Maybe a better example is one where you don't require the additional method:
(int value, string text) t = new ValueTuple<int, string>(21, "hello");
Again, you're not really naming the fields in the constructor syntax, but they are reinterpreted by the local variable declaration.
This is probably not a serious limitation. In a scenario where there's a desire to have a persistent, easily-assigned name, it's probably better to declare a user-defined type than to use the tuple syntax anyway. You can write deconstructors for user-defined types as well, and declaring types like that means the names are first-class citizens when it comes to reflection, dynamic
, etc.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…