Re:Scala's Option monad versus null-conditional operator in C#
by runT1ME on Saturday February 20, 2016 @05:39PM
(#11142310)
It's really not. I worked for a .NET shop that migrated some new projects to Scala. We evaluated F#, but decided the power of Scala was worth the platform switch. F# lacks higher kinds and implicit parameters, meaning you can't really use the type class pattern. This hurt our productivity.
[ Parent
| on HN ]
Re:Scala's Option monad versus null-conditional operator in C#
by louthy on Saturday February 20, 2016 @05:49PM
(#11142349)
> lacks higher kinds
It can be done in F# [1], but it's not pretty, and absolutely nails the compiler. The fact that the compiler can be cheated into doing it makes it even more frustrating that there isn't some official support.
Re:Scala's Option monad versus null-conditional operator in C#
by azth on Sunday February 21, 2016 @01:37AM
(#11143585)
> F# lacks higher kinds and implicit parameters, meaning you can't really use the type class pattern. This hurt our productivity.
Genuinely curious, but what are you doing that the lack of type classes hurts productivity so much?
Re:Scala's Option monad versus null-conditional operator in C#
by runT1ME on Sunday February 21, 2016 @02:29AM
(#11143677)
It's just annoying to have to re-implement sequence/traverse and every combination of monad stacks you want to for each type. It's doable, but bug prone and frustrating.
I now work for one of the largest scala teams in the US. We make heavy use of the Scalaz project and regularly use monad transormers or free monads and both require higher kinded types.