3 ms·
While there's nothing you can do in C# that cannot be done in F#, the reverse is not true. The biggest thing that comes to mind is to influence the direction o
by mikece 7y ago
While there's nothing you can do in C# that cannot be done in F#, the reverse is not true. The biggest thing that comes to mind is to influence the direction of the other language (C#). I've heard it said many times that if you want to see what features will be in C# in the future, look at F#. Too many features to cite (though Linq is the biggest that comes to mind) were in production use in F# long before they arrived in C#.
- McWobbleston 7y agoThere's actually a couple of minor things (like covariance). I was surprised to learn F# doesn't support creating sealed methods on classes the other week when I was extending some OO code. Thankfully F# and C# mix so well together I could've written a quick C# project to do it if needed, but I didn't want to break up my F# project into two + some C# glue In the vast majority of cases though what you said is true. Discriminated unions, records, computation expressions, and type providers are total game changers
- svick 7y ago> While there's nothing you can do in C# that cannot be done in F# Really? When did F# start supporting pointers? > to influence the direction of the other language (C#) Lately, it seems it's the other way around: C# is introducing features like Span<T> or default interface members and F# is (quickly) catching up.
- runevault 7y agoTo your last point, with the freedom they seem to feel after the Core breakage (like Span/Memory) C# might start innovating on its own again instead of just taking awesome pieces from f# and making them part of C#.