On Dec 13, 2011, at 5:09 AM, Bryan O'Sullivan wrote:
> Correct. And your example of "some (Just 1)" inflooping was not a
> counterargument, but rather an illustration that perhaps some people (and I'm
> not trying to imply you here, don't worry) don't understand what some and
> many are supposed to do.
But does it really make sense to have class methods with the property that they
are undefined on all but a special value of a type? It seems extremely silly
to me to keep these two methods in the class and to get around this problem by
adding documentation that essentially says, "Don't use these methods because
they are not actually defined in general."
Cheers,
Greg
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
