Fri Oct 7 20:09:53 EDT 2011
And the saga continues. I spend long times in total frustration not
understanding what a cryptic type error means when I'm playing with
type classes. Usually I just try to go about differently and succeed
to my great surprise. In short: I often really don't get it yet. At
those times I don't know where to actually look to understand why a
particular construct will not work.
The moral of the story is that just adding type signatures will often
solve the problem, and if it really doesn't work, it's probably a
conceptual error, i.e. try harder!