last monad thoughts before i pass out 

im pretty sure that if youre a working haskell programming, youre usually not going to be doing super exotic things with your monads. in fact youre probably not even going to be using the option or list monads (maybe for a bit of code golfing here and there).

many monads in haskell code are big monad transformer stacks, which really just means a thingy that lists which side effects are allowed to be performed by functions that wrap their return value around the monad. so youre not thinking about category theory stuff and composition operators youre really just thinking about side effects and how you want to tame them.

Follow

re: last monad thoughts before i pass out 

@iitalics certainly i found i could get away with treating a lot of monadic code as a state-passing style where i was effectively sequencing side effects

Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!