I have no idea what "imperative monads in Scala or Haskell" is, so I guess yes, it is a fantastic day for that!
-
This Tweet is unavailable.
-
Oh, ok, I thought it was rhetorical. I was just trying to give a working definition of "imperative monad". One that makes you feel like you're programming awkward Python. There's probably some IORefs or MVars in the reader context.
I still don't understand what makes it "imperative." If I pass a function around, is it imperative? What if I use the (>>=) instance for ((->) t)? I cannot make this definition work, sorry.
-
-
It's not a precise thing. Because after all, all Haskell code is eventually C, and all C code is eventually, um, transistors. It's about style.
-
Right, but what makes it imperative? Why did we call it imperative, and not say, purple? Because both adjectives appear equally applicable to me.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.