to serialise.
Simon
| -Original Message-
| From: Neil Mitchell [mailto:[EMAIL PROTECTED]
| Sent: 02 July 2007 22:26
| To: Aaron Tomb
| Cc: Simon Peyton-Jones; cvs-ghc@haskell.org
| Subject: Re: More External Core questions
|
| Hi Aaron,
|
| > So, yeah, perhaps External Core should b
Hi Aaron,
So, yeah, perhaps External Core should be essentially a textual
representation of a .hi file.
Textual is something I doubt has much benefit. Yhc.Core has no textual
syntax, and we've never wanted one. How about .hcr being just .hi but
with complete bodies for all functions?
If you d
I think I'm convinced. Trying to make the format stay consistent has
been the major thing that has slowed me down. The current syntax
doesn't include all of the information contained in the iface data
types, and inferring the missing bits is rather tricky. I had thought
that inference of th
Hi
From my viewpoint as a current user of GHC Core:
Things would actually be significantly easier if I dropped backward
compatibility and essentially just did a Read/Show approach.
Backward compatibility got broken a while ago, since GHC Core
currently doesn't seen to work. Given that you h
On Jul 2, 2007, at 2:28 AM, Simon Peyton-Jones wrote:
=| 2) I have the following source file:
|
|%module main:GADTTest
| %data main:GADTTest.Term x =
|{K :: %forall x a (cozuwild::(x:=:a -> a)) .
| main:GADTTest.Term x};
|
| which is translated into (roughly):
|IfaceData {
| 1) What's the right way to encode the coercion manipulation functions
| such as left, right, and sym as IfaceTypes?
They are just Types, so they'll convert straightforwardly to IfaceTypes. That
must be happening *already* because coercions appear in interface files.
| 2) I have the following
I'm slowly but surely making more progress on External Core. I can
now typecheck many simple programs, but I'm blocked on a number of
questions about the right way to encode various types in iface format.
1) What's the right way to encode the coercion manipulation functions
such as left, ri
