Changes to Typeable

I hate using things like 'new', 'old', 'unsafe' in module names, the
words are too overloaded and mean different things in different
contexts. you end up with things like 'NewerTypeable'. So why not call
it what it is already known by, 'Data.PolyTypeable'.
John
On Sat, Feb 11, 2012 at 5:05 PM, Roman Leshchinskiy <rl at cse.unsw.edu.au> wrote:
> On 10/02/2012, at 16:03, Simon Peyton-Jones wrote:
>>> Friends
>>>> The page describes an improved implementation of the Typeable class, making use of polymorphic kinds. Technically it is straightforward, but it represents a non-backward-compatible change to a widely used library, so we need to make a plan for the transition.
>>>>http://hackage.haskell.org/trac/ghc/wiki/GhcKinds/PolyTypeable>>>> Comments? You can fix typos or add issues directly in the wiki page, or discuss by email
>> IMO, polymorphic kinds are far too experimental at this stage to be used in such a fundamental library. I also fully agree with Ian's point about other implementations.
>> Should there perhaps be a NewTypeable module which could then be renamed into Typeable once it is sufficiently well established?
>> Roman
>>>> _______________________________________________
> Glasgow-haskell-users mailing list
>Glasgow-haskell-users at haskell.org>http://www.haskell.org/mailman/listinfo/glasgow-haskell-users