3 ms·
> it's followes a purely functional programming paradigm I'd say that it's one take on that paradigm, the Way of Monads is not the only way to do purely functi
by masklinn 7y ago
> it's followes a purely functional programming paradigm
I'd say that it's one take on that paradigm, the Way of Monads is not the only way to do purely functional, Clean uses uniqueness typing instead. Though it otherwise has rather similar properties to Haskell.
- deleted 7y ago[deleted]
- yeshengm 7y agoI'd say start with some eager functional language such as OCaml without the "object" part. Haskell code is hard to debug cuz you can't rely on good old print. Monad itself is never a silver bullet. Type systems and Composability are the true power of FP IMO.
- willtim 7y agoDebugging declarative code is always hard, whatever the language. Haskell does allow you to use trace expressions which will output values to standard out, see Debug.Trace. This is no reason to avoid arguably the most popular (and state-of-the-art) function language and implementation out there.
- marceloabsousa 7y agoI think we can all agree that debugging languages with lazy evaluation is specially hard. To effectively use Debug.Trace you actually need to add strictness and that can be fundamentally incompatible if you do intend to use the full power of lazy evaluation.
- lonelappde 7y agoDebug.Trace won't solve the space leaks lurking around every corner of your program, and won't shave the hundreds of megabytes to gigabytes of RAM the compiler needs for compiling a non trivial program with dependencies.
- hopia 7y agoIt's for runtime debug logging after all, not intended to solve those issues. Space leaks I'd like to read more about but writings about them are a bit hard to come by. Recommendations?
- bontaq 7y agoIt took me way too long to come across Trace, if it was more widely known I don't think we'd see so many "impossible to debug" related issues. It's great.