"We need a better name than monad because monad sounds too abstract
-
-
Replying to @puffnfresh
@puffnfresh in F# we call them computation expressions, but they can do some extra stuff2 replies 0 retweets 0 likes -
Replying to @rickasaurus
@rickasaurus@puffnfresh problem is F# misses the practical purpose of monads, to abstract on all monads.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh it sort of separates the monadic type from the code rewriting machinery in an interesting way though.1 reply 0 retweets 0 likes -
Replying to @rickasaurus
@rickasaurus@puffnfresh if it is the insignificant, superficial detail left after removal of all practical purpose, what is interesting?3 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh I think that's a bit unfair. F# had comprehensive async before haskell after all.1 reply 0 retweets 0 likes -
Replying to @rickasaurus
@rickasaurus@puffnfresh Haskell is not the point. F# completely misses the practical purpose of monads. Like C#.2 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh you have to understand that F# is severely limited by the C#/CLR compatibility constraint1 reply 0 retweets 0 likes
@rickasaurus @puffnfresh Sure I understand that.
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.