-
-
Replying to @puffnfresh
@puffnfresh As I said: on that abstraction level I agree. But practical example where specifically auto-flatMap of promises fails..?1 reply 0 retweets 0 likes -
Replying to @puffnfresh
@puffnfresh I was talking about specifically flatMap of promise chains. When using .then - not a theoretical .map1 reply 0 retweets 0 likes -
Replying to @jankrems
@puffnfresh So my question would be: could there be any function that expects Promise[Promise[T]] for good reasons?2 replies 0 retweets 0 likes -
Replying to @jankrems
@jankrems@puffnfresh without abstraction, even the slightest, there is no longer any point to the API. It's entirely rubbish.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh Well, imho an abstraction for its own sake without practical value is rubbish. PLs are tools in the end.2 replies 0 retweets 0 likes -
Replying to @jankrems
@dibblego@puffnfresh I'm not saying that an additional generic .map/.flatMap wouldn't be potentially valuable.2 replies 0 retweets 0 likes -
Replying to @jankrems
@jankrems@puffnfresh it's not generic. It's equivocal, unprincipled, overly specialised and therefore, just generally useless.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh Well, thing is: I used it and I used map/flatMap. "Boy, I sure wish it would NOT flatten those promises!" - never3 replies 0 retweets 0 likes
@jankrems @puffnfresh there is a difference between functor (map) and monad (flatMap), but one is not "better" than the other.
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.