Property assigned in constructor can use initializer instead

[rubberduck203]

Take advantage of C# 6.0's auto-property initializers.

1. If a Property has a read-only backing field.
2. If a Property has a private Setter, but is only set in the constructor.

The first case is a lot of (now) unnecessary code. The second is poor man's immutability (and not really all so immutable).

[Vannevelj]

The syntax for this feature is

public int MyProperty { get; set; } = 10;
public IList<int> MyProperty { get; } = new List<int>();

which provides a default value for the property. Note that this also works with a read-only property.

[rubberduck203]

That's the point of (2). Out of laziness, many of us create immutable from the outside properties when we could make immutable from everywhere. I was thinking this should catch those situations. I'm trying to formalize a test case to clarify.

[rubberduck203]

class Foo
{
     int SomeProp { get; private set; }

    Foo()
    {
        this.SomeProp = 100;
    }
}

Assume there are other members, but the only place this gets set is in the constructor. Then it could be rewritten like this.

class Foo
{
     int SomeProp { get; private set; } = 100;
}