On 10.02.2012 20: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
| Where is Proxy data type defined?
In the section The new Typeable class of
http://hackage.haskell.org/trac/ghc/wiki/GhcKinds/PolyTypeable
| Which instances should it have?
Well, Typeable, perhaps! But that is no so relevant here.
S
___
On Sun, Jan 29, 2012 at 5:12 PM, Austin Seipp mad@gmail.com wrote:
I've done so, and have an RC2 bindist that doesn't have a segfaulting
GHCi. I suppose this build should be advocated to Snow Leopard users.
I currently need a place to put the bindist. I'm about to send an
email to
Sorry, I got caught up doing a few other things the past few days.
I'll make a binary of the 7.4.1 release later today and upload it to
my code.haskell.org account and report back here (the uploading will
take as long as the build, due to bad internet right now...)
On Fri, Feb 10, 2012 at 12:56
On Fri, Feb 10, 2012 at 04:03:42PM +, Simon Peyton-Jones wrote:
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
Would it be useful to make 'Proxy' an unboxed type itself? so
Proxy :: forall k . k - #
This would statically ensure that no one accidentally passes ⊥ as a parameter
or will get anything other than the unit 'Proxy' when trying to evaluate it.
So the compiler can unconditionally elide the
On Fri, Feb 10, 2012 at 03:30:02PM -0800, John Meacham wrote:
something I have thought about is perhaps a special syntax for Proxy, like
{:: Int - Int } is short for (Proxy :: Proxy (Int - Int)). not sure whether
that is useful enough in practice though, but could be handy if we are
