I think the error message could be made clearer simply by emphasizing the fact
that type ambiguity over the lack of instances.
Ambiguous type variable 't0' arising from a use of
elem :: a -> t0 a -> Bool
caused by the lack of an instance 'Data.String.IsString (t0 Char)'
Either ad
On Sun, Aug 2, 2015 at 12:58 PM, Daniel Bergey wrote:
> On 2015-07-31 at 08:59, Simon Peyton Jones wrote:
> > Daniel Bergey wrote:
> > | How hard would it be to give a different error message instead of "No
> > | instance ..." when the type variable is ambiguous? I always find this
> > | err
On 2015-07-31 at 08:59, Simon Peyton Jones wrote:
> Daniel Bergey wrote:
> | How hard would it be to give a different error message instead of "No
> | instance ..." when the type variable is ambiguous? I always find this
> | error slightly misleading, since it seems to me that there are
> | m
Alain O'Dea writes:
> On 21 July 2015 at 13:31, Ben Gamari wrote:
>
>>
>> Hello everyone,
>>
>> Earlier today I merged a clean-up [1] to the master branch which
>> removed some #ifdefs which ensured that the tree could be built with GHC
>> 7.6
>>
>> Thomas Miedema correctly pointed out that some
