GHC passes type arguments, and it must pass them in the right order,
else all hell breaks loose. At a call site GHC generates
(>>=) t1 t2 foo (\x -> baz)
and t1, t2 had better be in the right order.
It's an internal-to-GHC thing really.
S
| -----Original Message-----
| From: Ross Paterson [mailto:[EMAIL PROTECTED]
| Sent: 13 February 2004 15:24
| To: Simon Peyton Jones
| Cc: [EMAIL PROTECTED]
| Subject: Re: cvs commit: fptools/libraries/base/GHC Base.lhs
|
| On Thu, Feb 12, 2004 at 06:55:06AM -0800, Simon Peyton Jones wrote:
| > simonpj 2004/02/12 06:55:06 PST
| >
| > Modified files:
| > libraries/base/GHC Base.lhs
| > Log:
| > Explicit for-alls for Monad (so desugaring knows which order to
give type args)
|
| Has something changed to make that necessary (or is it just for
clarity)?
_______________________________________________
Cvs-libraries mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-libraries
