4 ms·
FWIW, you can thank F# for C#'s level of polish. Don Syme was a (if not the) driving force behind .NET going with reified generics, for one. Also, back when I
by bunderbunder 9y ago
FWIW, you can thank F# for C#'s level of polish.
Don Syme was a (if not the) driving force behind .NET going with reified generics, for one. Also, back when I was a "C# by day, F# by night" developer, I really felt like F# was being used as an incubator for ideas that were eventually pulled into C# in some form or another. For example, in some respects async/await feels like a domesticated version of the async computation expression.
- bonesss 9y agoCompare where the two languages were, and look where we are now.. Lambdas? C# got them later. Immutable constructor patterns? C# got them later. A scripting environment? C# is trying. Pattern matching? C# is trying (but since it's not exhaustive...). No nulls by default? C# got it later (and less clearly). It's really impressive how quickly those features have gained mindshare and become 'must haves' despite initial resistance. Fundamentally, though, the higher order programming features that F# inherits ML give it a maturity and flexibility that C# will just never encompass.