News for hackers. Stuff that matters.
Re:Making Wrong Code Look Wrong by Bootvis on Monday August 22, 2011 @02:18PM (#2913437)
That comment illustrates the problem with Haskell. Yes it's nice and logical but for some reason also very hard.
Re:Making Wrong Code Look Wrong by pavpanchekha on Tuesday August 23, 2011 @09:32AM (#2916460)
This comment illustrates the problem with comments about problems with Haskell. It doesn't quite understand what it's complaining about.

Functor vs. Monad in this case is a way of talking about how exactly this construct should work --- it's not a meaningless distinction. As another response to my comment mentioned, both a functor or a monad are applicable. The question is whether two instances of this data type (I'm using non-Haskell-y terms for clarity) have influence on each other (in rough terms). So it's not that I was complaining that the parent was wrong. I was complaining that the semantics he was imposing on his quoted strings were too restrictive. Another poster instead mentioned ways in which mine were too loose. So my post was part of a constructive debate on what exactly we want quoted strings to do. That Haskell provides a vocabulary for communicating precisely and tersely is not it's fault, it is one of its strengths.

Re:Making Wrong Code Look Wrong by jrockway on Monday August 22, 2011 @02:22PM (#2913452)
Any monad is also a functor, so they're both right!
Re:Making Wrong Code Look Wrong by eru on Monday August 22, 2011 @04:36PM (#2914014)
Actually, he probably wants an applicative functor, which sits between functors and monads.

Or perhaps an arrow or a co-monad are better? ;o)

Re:Making Wrong Code Look Wrong by eru on Monday August 22, 2011 @04:37PM (#2914017)
> [...] but for some reason also very hard.

Yes. But that's a feature, not a bug.

Re:Making Wrong Code Look Wrong by gmartres on Tuesday August 23, 2011 @07:53AM (#2916205)
It's not hard, it's different.