Library hierarchy, contd.

[Simon Marlow]

> On Wed, May 23, 2001 at 05:43:01PM +0100, Simon Marlow wrote:
> > Edison                  -- (opt, uses multi-param type classes)
> >     Prelude             -- large self-contained packages should have
> >     Collection          -- their own hierarchy?  Like a=20
> vendor branch.
> >     Queue               -- Or should the whole Edison tree be placed
> >     ...                 -- under [Data.]Structures?
>=20
> In this particular instance, I'd like to use the Edison structures,
> and I'd like them to be available in a standard place.  But maybe this
> just means there should be copies of some of these libraries under the
> Data hierarchy.

The only reason that Edison is in a subtree of its own is that no-one
has "decided" what the API for the standard versions of these libraries
should be.  Maybe that choice will be to adopt Edison as-is, but that
would rule out using these modules from NHC because of Edison's use of
multi-parameter type classes.

Cheers,
	Simon