Target typing should work while performing record nondestructive mutation.

[HobbsCode]

Version Used:
.NET 5

Steps to Reproduce:
SharpLab

public record Person 
{ 
    public string Name {get; init;}    
}

public class Program
{   
    public static void Main() 
    {
        Person alice = new Person() with { Name = "alice" }; // OK
        Person bob = new() with { Name = "bob" }; // Error CS8754
        
        Console.WriteLine(alice);
        Console.WriteLine(bob);
    } 
}

Expected Behavior:
The program should compile without error.

Actual Behavior:
The compiler rejects the initialization of variable 'bob' with CS8754.

[CyrusNajmabadi]

I'm not getting the value here. if Person is a record, this would already work and woudl be shorter and clearer:

Person bob = new() { Name = "bob" };

[Joe4evr]

If I had a stake in this, I'd consider new Person() with { .... } to be a full-on compiler error as well:

1. It's double-allocating an object for completely no reason
2. It can actually break at runtime if/once the language gets that "final initializer" feature and the Person class adds one of those to throw if Name isn't set.

[HobbsCode]

One is legal while the other is not. Seems like they should be treated the same. I doubt anyone has taken any meaningful dependency on this behavior.

[Joe4evr]

True, though it's up to the LDT to determine if they want to make that happen.