Frank Atanassow wrote: > However, I think maybe it has demonstrated that the implicit > forall'ing in > Haskell can be confusing in practice. In particular, it makes > it hard to talk > unambiguously about types of non-top-level definitions/terms. I'm sure this pot has been stirred up enough already, but as a newbie to Haskell I also found the "forall" rules counter-intuitive with regard to exitential types. (i.e. the use of forall a. when exists a. might have been clearer.) I hope that at some point this area of Haskell will be revised. --Peter Douglass
- Re: more detailed explanation about forall in Ha... Jan Brosius
- RE: more detailed explanation about forall in Ha... Mark P Jones
- Re: more detailed explanation about forall ... Claus Reinke
- Re: more detailed explanation about forall in Ha... Lennart Augustsson
- Re: more detailed explanation about forall ... Jan Brosius
- Re: more detailed explanation about forall in Ha... Frank Atanassow
- RE: more detailed explanation about forall in Ha... Frank Atanassow
- Re: more detailed explanation about forall in Ha... Ketil Malde
- Re: more detailed explanation about forall ... Frank Atanassow
- Re: more detailed explanation about forall ... Lars Lundgren
- Re: more detailed explanation about forall in Ha... Peter Douglass
- Re: more detailed explanation about forall in Ha... Jan Brosius
- Re: more detailed explanation about forall in Ha... Lennart Augustsson
- Re: more detailed explanation about forall ... Iavor Diatchki
- RE: more detailed explanation about forall in Ha... Peter Douglass
- Re: more detailed explanation about forall ... Jan Brosius
- Re: more detailed explanation about forall in Ha... Peter Hancock
- Re: more detailed explanation about forall ... Keith Wansbrough
- Re: more detailed explanation about forall in Ha... Marcin 'Qrczak' Kowalczyk
- Re: more detailed explanation about forall in Ha... Marcin 'Qrczak' Kowalczyk