Required init with backing field gives null warning

[JoasE]

Having a required init property which sets a backing field still gives a null warning.
Is this a bug?

The below code gives a warning: Warning CS8618 Non-nullable field '_name' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.

public class TestRequiredInit
{
    private readonly string _name;

    public required string Name
    {
        get => _name;
        init => _name = value;
    }
}

I don't see a way to create TestRequiredInit without _name being set to a non nullable value without producing warnings, se the warning it produces now doesn't make sense to me.

Doing this with constructor instead of required init doesn't produce a warning.

public class TestConstructor
{
    private readonly string _name;

    public TestConstructor(string name)
    {
        _name = name;
    }

    public string Name
    {
        get => _name;
    }
}

[333fred]

As it currently stands, this behavior is expected. However, we will be discussing a possible improvement to the scenario in LDM on Wednesday: #6754.

[333fred]

Note for posterity: LDM approved making a change here, MemberNotNullAttribute on Name can be used in this scenario.