No, looking at the definitions from section 7.6.10 of the C# spec, an object-or-collection-initializer
expression is either an object-initializer
or a collection-initializer
.
An object-initializer
is composed of multiple member-initializer
s, each of which is of the form initializer = initializer-value
whereas a collection-initializer
is composed of multiple element-initializer
s, each of which is a non-assigment-expression
.
So it looks like it's by design - possibly for the sake of simplicity. I can't say I've ever wanted to do this, to be honest. (I usually wouldn't derive from List<int>
to start with - I'd compose it instead.) I would really hate to see:
var obj3 = new MyList { 1, 2, Text = "Hello", 3, 4 };
EDIT: If you really, really want to enable this, you could put this in the class:
class MyList : List<int>
{
public string Text { get; set; }
public MyList Values { get { return this; } }
}
at which point you could write:
var obj3 = new MyList { Text = "Hello", Values = { 1, 2, 3, 4 } };
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…