A type is, well, a type.
A type class is a relation between types.

The confusion probably comes from OO programming 
where (interfaces) describe unary relations (= one parameter type classes).

(begin rant) I wouldn't easily give up algebraic data types 
just because OO programmers don't seem know about them -
so the re-invent them and call it "composite" pattern...



_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to