Gauthier Segay

`type Stocks = CsvProvider< const(__SOURCE_DIRECTORY__ + "/MSFT.csv") >` is how I do it, which works with all versions of compilers and the library.

There is a language suggestion regarding provided DU & records: https://github.com/fsharp/fslang-suggestions/issues/154 And another one to be able to pass types to type providers: https://github.com/fsharp/fslang-suggestions/issues/212

related: https://github.com/fsharp/fslang-suggestions/issues/729

It is hard for me to comment without understanding more about code where you'd use it. It would help me if you'd had samples of before/after added to the suggestion....

@voronoipotato the issue with the examples provided in your post is the loss of parameter names (and their documentation?) I actually like the approach of unifying the signature file syntax...

I encounter similar patterns in my code, but it is rare that it is simple field access among the DU cases, it generally involves additional logic, so I'll likely not...

Without going with implementing the suggestion, fsc could be improved to recognise the mistake and prompt the user to correct to the appropriate syntax. currently: ```fsharp type Demo = abstract...

@qrzychu can't you still consume them via the constructor syntax, but just not use the init property syntax?  From what I see, it is possible to consume C# records...

> At some point, we will add support for the compile-time checks, just like we did with Span and friends. If I understand correctly, the runtime doesn't forbid setting of...

There is one pitfall I see, around the "setter in method call" feature of F#: ```csharp public class NiceInit { public NiceInit() {} public int Val {get; init;} } ```...