Assignment to readonly property in initializer list

Question

Can one tell me, why the heck does it compile?

namespace ManagedConsoleSketchbook
{
    public interface IMyInterface
    {
        int IntfProp
        {
            get;
            set;
        }
    }

    public class MyClass
    {
        private IMyInterface field = null;

        public IMyInterface Property
        {
            get
            {
                return field;
            }
        }
    }

    public class Program
    {
        public static void Method(MyClass @class)
        {
            Console.WriteLine(@class.Property.IntfProp.ToString());
        }

        public static void Main(string[] args)
        {
            // ************
            // *** Here ***
            // ************

            // Assignment to read-only property? wth?

            Method(new MyClass { Property = { IntfProp = 5 }});
        }
    }
}

score 13 · Accepted Answer · answered Apr 03 '13 at 10:13

This is a nested object initializer. It's described in the C# 4 spec like this:

A member initializer that specifies an object initializer after the equals sign is a nested object initializer - that is, an initialization of an embedded object. Instead of assigning a new value to the field or property, the assignments in the nested object initializer are treated as assignments to members of the field or property. Nested object initializers cannot be applied to properties with a value type, or to read-only fields with a value type.

So this code:

MyClass foo = new MyClass { Property = { IntfProp = 5 }};

would be equivalent to:

MyClass tmp = new MyClass();

// Call the *getter* of Property, but the *setter* of IntfProp
tmp.Property.IntfProp = 5;

MyClass foo = tmp;

OK, now that's clear. It's a confusing piece of syntax, though. — Spook, Apr 03 '13 at 10:15

bas · Answer 2 · 2013-04-03T10:17:04.733

1

Because you are using the initializer which uses the setter of ItfProp, not the setter of Property.

So it will throw a NullReferenceException at runtime, since Property will still be null.

edited Apr 03 '13 at 10:17

answered Apr 03 '13 at 10:11

bas

13,550
20
69
146

Can you elaborate? How does the standard cover this situation? – Spook Apr 03 '13 at 10:12
hang on, booting visual studio, post some clarifying example – bas Apr 03 '13 at 10:13
2

ah, Jon is in the house, I can't compete with him :p – bas Apr 03 '13 at 10:14
@Spook, make no mistake, `Property` will still be `null`. – bas Apr 03 '13 at 10:18

score 0 · Answer 3 · answered Apr 03 '13 at 10:15

0

Because

int IntfProp {
    get;
    set;
}

is not readonly.

You did not invoke setter of MyClass.Property, just getter.

answered Apr 03 '13 at 10:15

Ken Kin

4,503
3
38
76

Assignment to readonly property in initializer list

3 Answers3

Linked