Defining a property in a record twice

Question

In C# 9, one can define a property with the same name in a record both in its primary constructor and in its body:

record Cat(int PawCount)
{
    public int PawCount { get; init; }
}

This code compiles without errors.

When initializing an instance of such a record, the value provided to the constructor is completely ignored:

Console.WriteLine(new Cat(4));
Console.WriteLine(new Cat(4) { PawCount = 1 });

prints

Cat { PawCount = 0 }
Cat { PawCount = 1 }

---

Is this behavior correct or is it a bug? If it’s correct, what are the cases in which it is useful?

I expected the compiler to either reject this code with an error like ‘The type Cat already contains a definition for PawCount’ or consider the property in the constructor and in the body the same, performing its initialization from the constructor. The latter variant could be useful to provide the property with a custom getter and/or initializer without having to rewrite all the properties of the positional record in its body.

The actual behavior makes no sense to me.

Answer 1

The correct way to do this is:

record Cat(int PawCount)
{
    public int PawCount { get; init; } = PawCount;
}

This is useful as it allows you to do e.g. validation

record Cat(int PawCount)
{
    private int _pawCount;
    public int PawCount {
        get => _pawCount;
        init => _pawCount = value < 0 ? throw new ArgumentException() : value; 
    } = PawCount;
}

The spec for this is here: https://github.com/dotnet/csharplang/blob/master/proposals/csharp-9.0/records.md#members-of-a-record-type

Members are synthesized unless a member with a "matching" signature is declared in the record body or an accessible concrete non-virtual member with a "matching" signature is inherited. Two members are considered matching if they have the same signature or would be considered "hiding" in an inheritance scenario.

So since a property with the same name as the parameter already exists, the compiler wont synthesize a PawCount property, and so just silently ignores the parameter unless you use it yourself explicitly.