Naming types

[Sean Leather]

> As we push the boundary on Haskell's type system, so that types and values
> blur a bit more, Haskell's deliberate overlapping of type constructor and
> data constructor name space is becoming a little awkward.   Syntax is
> tiresome, but it's unavoidable.
>
> I've written down the issues and made some proposals here.
> http://hackage.haskell.org/trac/ghc/wiki/Design/TypeNaming
>  <http://www.haskell.org/mailman/listinfo/cvs-ghc>

A few questions:

What purpose does the "type" disambiguating specifier serve in proposal 1?
Don't type synonyms have the same namespace as datatypes? It would make
sense to me to match (export specifier<->declaration) data<->data,
newtype<->newtype, and type<->type for explicit documentation purposes in
the export list rather than combine data and newtype into data and leave
type as type.

Will the currently chosen shift operator % conflict with any infix type
operators using %?

Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.haskell.org/pipermail/cvs-ghc/attachments/20080923/236bc04e/attachment-0001.htm