-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/3/10 21:30 , Maciej Piechotka wrote:
On Tue, 2010-11-02 at 21:57 -0400, Brandon S Allbery KF8NH wrote:
On 10/29/10 09:35 , Dominique Devriese wrote:
* Only introduce a dependency from type class A to type class B if all
functions in type
Sönke Hahn schrieb:
I have been thinking for a while that it might be worth defining a
Prelude2, which corrects the known problems with the Prelude. Over time,
people could migrate to using Prelude2. It would probably take years to be
widely adopted, but at least there would be light at the
On Tue, 2010-11-02 at 21:57 -0400, Brandon S Allbery KF8NH wrote:
On 10/29/10 09:35 , Dominique Devriese wrote:
* Only introduce a dependency from type class A to type class B if all
functions in type class B can be implemented in terms of the
functions in type class A or if type class
I've been thinking about the following type class design principles:
* Only include two functions in the same design class if both can be
implemented in terms of each other.
* Only introduce a dependency from type class A to type class B if all
functions in type class B can be
I have been thinking for a while that it might be worth defining a
Prelude2, which corrects the known problems with the Prelude. Over time,
people could migrate to using Prelude2. It would probably take years to be
widely adopted, but at least there would be light at the end of the
tunnel.
