!
Simon
From: Richard Eisenberg [mailto:e...@cis.upenn.edu]
Sent: 07 March 2016 05:00
To: Simon Peyton Jones <simo...@microsoft.com>
Cc: Christopher Allen <c...@bitemyapp.com>; ghc-devs@haskell.org
Subject: Re: Specialized type hints
I, for one, would greatly welcome someone re
ld all be
> amazing.
>
> Simon
>
> From: Christopher Allen [mailto:c...@bitemyapp.com]
> Sent: 04 March 2016 16:24
> To: Simon Peyton Jones <simo...@microsoft.com>
> Cc: ghc-devs@haskell.org
> Subject: Re: Specialized type hints
>
> I was looking for
changes; debate them with others to form a
consensus about what would be good; implement them… that would all be amazing.
Simon
From: Christopher Allen [mailto:c...@bitemyapp.com]
Sent: 04 March 2016 16:24
To: Simon Peyton Jones <simo...@microsoft.com>
Cc: ghc-devs@haskell.org
Subject: Re: Speci
I was looking for an indication that a more general type error improvement
sweep would be welcome. I could pinpoint a particular type error if you
liked (such as the one that prompted this email), but there are general UX
improvements I would like to undertake.
On Fri, Mar 4, 2016 at 4:25 AM,
Christopher
Improving error message is an excellent goal, and one that I have spent more
hours on than I care to tell you.
If you have a particular one in mind, could you open a Trac ticket with a
particular reproducible test case, the error message you get, and the error
message you’d like
On Thu, Mar 3, 2016 at 11:58 AM, Eric Seidel wrote:
> On Wed, Mar 2, 2016, at 23:54, Christopher Allen wrote:
> > I'd like to see how warm people would be to catching GHC's type error
> > quality up a bit.
> >
> > I did a write-up on a confusion a reader of our book had:
> >
> >
On Wed, Mar 2, 2016, at 23:54, Christopher Allen wrote:
> I'd like to see how warm people would be to catching GHC's type error
> quality up a bit.
>
> I did a write-up on a confusion a reader of our book had:
>
> https://gist.github.com/bitemyapp/c27c721b92dab0248433
Wow, this is a pretty