Re: [Haskell] reasons for non-portability

2004-03-21 Thread Sven Panne
Wolfgang Jeltsch wrote: [...] My question is, if a module is considered non-portable only if it contains non-portable constructs itself, or if a module is also non-portable if it just imports a module which is non-portable. Both, otherwise stating the property "portable" wouldn't help very much. Th

Re: [Haskell] reasons for non-portability

2004-03-21 Thread Wolfgang Jeltsch
Am Sonntag, 21. März 2004 12:36 schrieben Sie: > Wolfgang Jeltsch wrote: > > [...] My question is, if a module is considered non-portable only if it > > contains non-portable constructs itself, or if a module is also > > non-portable if it just imports a module which is non-portable. > > Both, othe

[Haskell] deriving with newtypes

2004-03-21 Thread Wolfgang Jeltsch
Hello, I'm trying to use GHC's deriving mechanism for newtypes in the following way: class C a b instance C [a] Char newtype T = T Char deriving C [a] Unfortunately, this isn't possible. Is there a reason for this? Can I circumvent this restriction? Wolfgang

Re: [Haskell] Haddock, QuickCheck, and Functional Design by Contract

2004-03-21 Thread Dylan Thurston
(Reviving an old message here. You can see the original message at http://www.stud.tu-ilmenau.de/~robertw/haskell/doc/contract_notations.lhs ) On Tue, Feb 17, 2004 at 10:50:30AM +0100, Robert Will wrote: > 4. A notation for preconditions. ... >Presently I use the following coding style: > >

Re: [Haskell] Proposal for a Standard of Abstract Collections (with Reference Implementation)

2004-03-21 Thread Dylan Thurston
It looks interesting and I'm still looking at it, although I think many of the language extensions need to be better thought out. But it exhibits the "creeping Eq" problem: your hierarchy starts class (Eq (coll a), Eq a) => Collection coll a where ... If this is to replace lists, this is un