On Wed, 15 Jul 1998, Simon L Peyton Jones wrote:
> For these
>
> > * multi-parameter type classes
> > * existential types
> > * exceptions
> > * mutually recursive import [GHC does this ok]
>
> we'll have a shiny new GHC beta release before ICFP (end Sept).
> (I.e. it's pretty much working now.) Don't know about Hugs.
My understanding from Alastair was that Hugs was being synchronized with
GHC so that it could using precompiled GHC libs. Wouldn't that require
that it support these features as well? (I has also assumed that a
perl-like "eval" function would then become part of GHC/Hugs -- but that
may have been unwarranted)
> > * require/ensure/invariant assertions (my optimism)
>
> We need an agreed design first. Your point about putting
> asertions in type signatures makes me think that maybe assertions
> would be premature for Std Haskell.
Does that mean they will or won't be in GHC/Hugs? I am treating GHC/Hugs
as the standard so "Std. Haskell" is less interesting.
> > * module signatures/dynamic linking
> > * dynamic linking (serialization/persistence?)
> I'm hazy about what you have in mind here.
I saw module signatures on your todo list for 2.0 and was not sure to
what it referred. I was thinking it was short-hand for fixing the Haskell
module system:
* mutual recursive imports
* a sane scheme for module name space (i.e. support for packages)
* multiple privacy levels (e.g. module vs package vs public)
* import-chasing as part of the spec
* dynamic linking to precompiled binaries when available
-Alex-
___________________________________________________________________
S. Alexander Jacobson i2x Media
1-212-697-0184 voice 1-212-697-1427 fax
