seq as type class method

[Henning Thielemann]

On Fri, 6 Nov 2009, Stefan Holdermans wrote:

> Henning,
>
>> Sure, but why was this a problem? Because they had to re-arrange a lot, and 
>> had to change the signature each time. But once that re-arrangement 
>> settles, it would be nice to have the Seq type constraint, right?
>
> I cannot tell whether *I* would find it problematic in practice. Hudak et al. 
> write:
>
> "However, the limitations of this solution soon became apparent.
> Inspired by the Fox project at CMU, two of Hughes’s students
> implemented a TCP/IP stack in Haskell, making heavy use of
> polymorphism in the different layers. ...

Yes, I think that this is the paragraph that can also be found in the 
History of Haskell. I might add that better refactoring tools could also 
have been a solution, right?