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.
-
-
I would say imperative monad = XT IO for some X ? I.e. the "main monad" of most real world programs, unfortunately.
1 reply 0 retweets 2 likes -
What makes it "imperative"? And what does the IO monad have to do with IO?
1 reply 0 retweets 0 likes -
Pretty sure you are smart enough to know what I mean. Could you give me your point in form that is not a question?
2 replies 0 retweets 0 likes -
I don't have a point, other than, trying to understand what you might mean.
1 reply 0 retweets 0 likes -
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.
3 replies 0 retweets 1 like -
It's named after the program itself, probably <Program>M. It appears in roughly half the type signatures of the project. The sight of it makes the viewer daydream of the days when FP still felt interesting. Its best friend is "-- TODO: refactor"
1 reply 0 retweets 1 like
I think if IO appears in half your project, you're doing it wrong. It hasn't yet appeared in a project that I started last year and is now 50KLOC.
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.