Phillip Carter
Phillip Carter
@ebresafegaga The next step would be an RFC here: https://github.com/fsharp/fslang-design Although starting off with some coding isn't a bad idea either, it's often a good idea to flesh out a...
Labeling as a bug due to not wanting to leak the type ID here. The missing constraint is correct though.
Yeah, this should raise an error. In C# an error is raised unless it is a literal or `null` passed in. There are two issues here, really: * this one,...
I think this is actually a bug, as it should be allowed but with a warning. Here's what it is with `trait`: ``` Microsoft (R) F# Interactive version 10.4.0 for...
@reinux as a general principle we want to avoid context-sensitive keywords as much as possible. I'd defer to @dsyme on this particular case for deprecating `params` as a reserved future...
This is handy in code instrumentation scenarios (e.g., OpenTelemetry) where you want as little overhead as possible but still want to do a little string formatting for messages on constructs...
@realparadyne > Could this become an interop pain point yes and no. Yes, insofar as there will be new methods in .NET 6 (not many) that take on in as...
Tagging https://github.com/dotnet/fsharp/issues/3508 and https://github.com/dotnet/fsharp/issues/9717
@dsyme @KevinRansom I will put this into 16.10 because we should get this done and unblock critical pieces of the TP ecosystem like fsharp.data
This also impacts SqlProvider I believe: https://devblogs.microsoft.com/dotnet/f-and-f-tools-update-for-visual-studio-16-9/#comment-8793