Phillip Carter
Phillip Carter
Some additional motivation: https://www.reddit.com/r/programming/comments/e8wfsr/discriminated_unions_in_c_an_unexceptional_love/fagb0hv/
I think this feature would be great for F# vNext as-suggested (and modulo some details in an RFC of course)
Just a note on IntelliSense, there are some things it helps with today: * By being after a `{` we know we're inside of a record * Typing anything in...
Also worth noting that the only sane way to construct records and ensure they work without issue with other lang constructs and refactorings is to apply even more verbosity: https://docs.microsoft.com/en-us/dotnet/fsharp/style-guide/formatting#formatting-records
Generally I think I'm in favor of doing this. @dsyme thoughts?
@charlesroddie Would you like to take a stab at an RFC for this?
Interesting discussion. I wouldn't support something along the lines of Haskell or Elixir-style lambdas, because instead of shortening what's already there, that would replace it with a new symbol. I'm...
Good point, `=>` would make cases like that unambiguous.
Although not called out explicitly, this is likely to fall under the following principle for anonymous records: https://github.com/fsharp/fslang-design/blob/main/FSharp-4.6/FS-1030-anonymous-records.md#design-principle-not-anonymous-object-expressions I can appreciate that anonymous records being a convenient substitute for a...
The challenge to this is that `IAsyncDisposable` is not available in .NET Standard 2.0, so we can't depend on the type directly in FSharp.Core. The type shape would have to...