On 24 November 2011 16:46, José Pedro Magalhães wrote:
> Hi Bas,
>
> On Thu, Nov 24, 2011 at 09:23, Bas van Dijk wrote:
>>
>> Hello,
>>
>> Now that we have DefaultSignatures, why is it not allowed to have
>> multiple default method implementations, as in:
>>
>> {-# LANGUAGE DefaultSignatures #-}
Hi Bas,
On Thu, Nov 24, 2011 at 09:23, Bas van Dijk wrote:
> Hello,
>
> Now that we have DefaultSignatures, why is it not allowed to have
> multiple default method implementations, as in:
>
> {-# LANGUAGE DefaultSignatures #-}
>
> class Foo a where
>foo :: a
>foo = error "foo"
>
>def
This deserves a wider audience: if you've encountered failures when
compiling FFI code with recent GHCs due to the new requirement that
newtypes be non-abstract, note that this will now be a warning, not an
error, in 7.4.1. We're deferring turning it into an error until 7.6.1.
Cheers,
Hello,
Now that we have DefaultSignatures, why is it not allowed to have
multiple default method implementations, as in:
{-# LANGUAGE DefaultSignatures #-}
class Foo a where
foo :: a
foo = error "foo"
default foo :: Num a => a
foo = 1
GHC complains: "Conflicting definitions for
