On Mon, Mar 17, 2008 at 05:32:01PM -0400, Samuel Bronson wrote:
On 3/17/08, John Meacham
wrote: yeah, that doesn't surprise me that much, though it will likely be not too hard to fix. basically, since we need to sometimes treat types as values we can scrutinize (->) has a reified form of the type constructor that takes two arguments named Jhc@.-> defined in Name.Names as tc_Arrow.
Code just needs to make sure that it translates between the two forms as needed.
That's easy for you to say... but JHC doesn't seem to get the kind right on (->) at this point...
Well, the kind of (->) is fairly tricky due to the fact it is kind-polymorphic for the same reason it is in ghc. since functions need to accept unboxed arguments and return unboxed tuples. Though, restraining it to * -> * -> * in class heads probably makes sense. John -- John Meacham - ⑆repetae.net⑆john⑈