Re:Generic Programming Made Easy in F#
by catnaroek on Friday December 15, 2017 @10:21PM
(#15937236)
> Concrete example: It doesn't have typeclasses.
It's not like type classes are themselves suuuper-principled.
> Being able to interoperate with .NET is a strength, not a weakness.
Being able to interoperate with .NET is a good thing. Letting the .NET object model permeate the whole language's type structure is less of a good thing (to put it mildly). OCaml did the right thing w.r.t. objects: You can use objects if you so wish, but the language doesn't ram them down your throat.
Re:Generic Programming Made Easy in F#
by tueo23094 on Friday December 15, 2017 @11:18PM
(#15937635)
F# and OCaml are different languages with different goals. It should come as no surprise there are different sacrifices between the languages.
Breaking compatibility with .NET, which is F#'s biggest benefit is counter productive.
Re:Generic Programming Made Easy in F#
by catnaroek on Saturday December 16, 2017 @05:26AM
(#15938849)
My suggestion wouldn't “break compatibility” with .NET any more than, say, C++/CLI (or whatever it is called nowadays) does.
Concrete example: It doesn't have typeclasses. This was a deliberate and thoughtful move. The designers haven't been able to figure out how to implement type classes in a way that wouldn't interact poorly with the rest of the .NET ecosystem, so they've opted to keep them out rather than introducing a hacky implementation. Contrast this with Scala, where it's very easy to accidentally break compatibility with Java code when you're working with traits.