Gauthier Segay

@njlr, not sure if this answers your question, but it is based on type abbreviation syntax: https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/type-abbreviations What is nice about them, compared to [C# using alias](https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/using-directive#using-alias) is that they...

Related: https://github.com/dotnet/csharplang/issues/477

> Another con to this is that you can achieve this today by setting warnings as errors, Actually, I'm not able to achieve this today, if matches use wildcards, adding...

@theprash great question! I'm eager to see what other think about potential issues / inconsistencies that would make the feature useless or if it can be made sound / respecting...

@Swoorup > I dislike sprinkling the language with attributes here and there. That implementation detail doesn't impact at all the consumption side, so it is a minor concern to me....

@vzarytovskii, thanks! I probably miss other features in the top bullet list that need to be considered, but could you expand on what you mean about "converting" as I am...

@dsyme, a minor comment on > The construction syntax for C# records is `R(X=1, Y=2)` and works today. I think `R(1,2)` also works, and it is kind of not great....

> @vzarytovskii: I guess this is one the controversial things, whether we want F# record syntax for C# records. > @dsyme My understanding is that these are positional parameters in...

Another point to consider is pattern matching, which has special syntax support in F#. Related: #968, caveat: https://github.com/fsharp/fslang-suggestions/issues/968#issuecomment-854072613 > @dsyme: I actually really dislike the use of { ... }...

@matthewcrews I think this is not an option, the BCL is going to use this pervasively. One option would be to not be able to define the interfaces with such...