Don Syme

I don't really understand the technical proposal here. I believe replacing the default ToString implementations just won't be possible without breaking compat - that is, in some sense the existing...

> Just so that you know how painful this is, take a look at our workaround's diff: Well, it's painful because you were running on an incomplete .NET implementation. I'm...

> how do I deal with this issue I don't really know, sorry. My vague understanding is that other routes have since opened up for publishing to Windows Store using...

I do go back and forth on this stuff. When optimistic I say "yes, sure", when realistic I say "no, compat". The history of this goes back so far. *...

@mrange String interpolation uses `%O` for unadorned `{ ... }`, which is current culture, but you can use the same formatting specifiers as `sprintf` which also giving increased type safety,...

@charlesroddie I'm glad you like it as a potential way forward. It seems tractable and I think the stakeholders at Microsoft/.NET w.r.t. backwards compat (myself and those responsible for delivering...

I'm inclined not to do "type inference on record field names" for C# record types. My initial thought is not do "record constructor syntax { X = 1; Y =...

As an aside, just noting a technical matter: For `{ csharpRecord with P=1 }` a generic record type can't change generic parameter. This is the same as for F# records:...

There's another question whether C# records can be used as inputs to anonymous record syntax, e.g. `{| csharpRecord with Z = 1 |}` F# records **can** be used as inputs...

> I think R(1,2) also works, and it is kind of not great. IMO, it should be giving a warning similar to https://github.com/fsharp/fslang-design/blob/main/drafts/FS-1095-requirenamedargumentattribute.md My understanding is that these are positional...