3 ms·
> monads are "imperative" hacks to make functional programming useful in any real-world-related way Monads are a quite clever solution to control IO: instead o
by TazeTSchnitzel 11y ago
> monads are "imperative" hacks to make functional programming useful in any real-world-related way
Monads are a quite clever solution to control IO: instead of allowing functions to directly perform IO, allow them to compose a sequence of IO operations and return them, such that you can compose a program which the runtime will then execute.
They're not imperative: they represent programs in a purely functional way, and they don't let you opt out of any of the guarantees a purely functional language provides. And they're not a hack, they fit properly into the type system.
Unlike "mostly functional" programming, use of monadic IO in a purely functional language will force you to cleanly separate IO and computation. Not only does this make a more maintainable program (no side effects everywhere), but you get nice bonuses, like lazy computation.
> and most monad tutorials will only confuse you about what they are actually.
Perhaps because many monad tutorials try to hide how they work, despite this really being quite simple.
- klibertp 11y ago> use of monadic IO in a purely functional language will force you to have `unsafePerformIO` in the language.
- TazeTSchnitzel 11y agoGHC has `unsafePerformIO` in order to implement pure abstractions. It's an implementation detail, Haskell proper does not support it, and you wouldn't use it in your code.
- deleted 11y ago[deleted]
- klibertp 11y ago> and you wouldn't use it in your code Speak for yourself. I don't see any value in not using a tool when it's available and seems to do the job: http://science.raphael.poss.name/haskell-for-ocaml-programmers.html#print-debugging http://science.raphael.poss.name/haskell-for-ocaml-programme... Personally I don't believe in 100% pure FP, it's both a pain in the ass and doesn't really give you more than 85% FP already would. Actually, most of the FP world seems to agree: out of many Lisps, Scala, OCaml, SML, F#, Erlang/Elixir etc. only Haskell is that hell-bent on purity. Even things like PureScript are more pragmatic than Haskell in this regard. Here's a great talk on getting what's best from FP without also taking all the problems: http://www.infoq.com/presentations/functional-pros-cons http://www.infoq.com/presentations/functional-pros-cons
- tome 11y ago> Even things like PureScript are more pragmatic than Haskell in this regard Interesting. In what way?
- TazeTSchnitzel 11y ago> Personally I don't believe in 100% pure FP, it's both a pain in the ass and doesn't really give you more than 85% FP already would. How so? Having a pure language has some significant benefits, like laziness. Data structures as control flow is awesome.
- viraptor 11y agoI've been very excited by many approaches before, then Haskell, and now I'm past it. While pure functional language will force you to cleanly separate computation and IO, with an app big enough you'll find yourself one day in a situation where independent data from 3 different places comes together in a way that the only reasonable way to proceed is to log a warning, tweak the value, and continue the computation. And that's what you'll do in any unpure language. In a pure one, you'll start to think how to redesign the computation to allow this... It's not wrong, but in many cases it's pointless.
- TazeTSchnitzel 11y ago> In a pure one, you'll start to think how to redesign the computation to allow this... It's not wrong, but in many cases it's pointless. Are you sure it's pointless? Having to show I/O in the type signature means you can't end up with accidental side-effects.
- viraptor 11y agoIn some cases - yes, pointless. You rarely care if a function logs something or not. If you do care, you can still return the log lines as an extra value and use the pure solution. At least you have a choice.
- marcosdumay 11y agoYou either add the logs as type annotations, or you run it inside a logging monad (not IO).