Re: type error formatting

A diff is up at https://phabricator.haskell.org/D1427 On Sat, Oct 24, 2015 at 1:14 PM, Evan Laforge wrote: > Ok, ticket created. I'll go see how much I can figure out on my own. > > https://ghc.haskell.org/trac/ghc/ticket/11014 > > WRT the "bound at" bits in "relevant

Re: type error formatting

On Fri, Oct 23, 2015 at 10:48 PM, Evan Laforge wrote: > Here's a typical simple type error from GHC: > > [...] > > I've been having more trouble than usual reading GHC's errors, and I finally > spent some time to think about it. The problem is that this new "relevant >

Re: type error formatting

Hi, Am Samstag, den 24.10.2015, 13:14 -0700 schrieb Evan Laforge: > WRT the "bound at" bits in "relevant bindings", I have no strong > opinion.  What about omitting them if they are in the same file as > the main error?  Or maybe they always are?  I'm not totally clear how > it chooses which

Re: type error formatting

> On 25 Oct 2015, at 21:21, Joachim Breitner wrote: > > Am Samstag, den 24.10.2015, 22:30 +0200 schrieb MigMit: >> At the very least, "bound at" should help IDEs (Emacs in particular) >> show exactly the right places. > > an IDE that offers such a deep integration

Re: type error formatting

Hi, Am Sonntag, den 25.10.2015, 21:30 +0100 schrieb MigMit: > Doesn't seem worth it to me. Current format is quite parseable, and > not really bad for human eyes either. I know that you meant this as a litote, but let me ignore that I know that for a moment to reply, that “not really bad” is

Re: type error formatting

> On 25 Oct 2015, at 21:45, Joachim Breitner wrote: > > Hi, > > Am Sonntag, den 25.10.2015, 21:30 +0100 schrieb MigMit: >> Doesn't seem worth it to me. Current format is quite parseable, and >> not really bad for human eyes either. > > I know that you meant this as a

Re: type error formatting

This looks like an improvement to me. I love the idea of a visual demarcation between sections, too; the bullets seem like a good choice there (the horizontal lines seem like they'd take up more space). Ryan On Sat, Oct 24, 2015 at 6:07 AM, Roman Cheplyaka wrote: > I have

RE: type error formatting

I’m all for it. Can advise. (Make a ticket.) Thanks! Simon From: Glasgow-haskell-users [mailto:glasgow-haskell-users-boun...@haskell.org] On Behalf Of Evan Laforge Sent: 24 October 2015 03:48 To: GHC users Subject: type error formatting Here's a typical simple type error from GHC:

Re: type error formatting

At the very least, "bound at" should help IDEs (Emacs in particular) show exactly the right places. > On 24 Oct 2015, at 22:14, Evan Laforge wrote: > > Ok, ticket created. I'll go see how much I can figure out on my own. > > https://ghc.haskell.org/trac/ghc/ticket/11014 >

Re: type error formatting

Ok, ticket created. I'll go see how much I can figure out on my own. https://ghc.haskell.org/trac/ghc/ticket/11014 WRT the "bound at" bits in "relevant bindings", I have no strong opinion. What about omitting them if they are in the same file as the main error? Or maybe they always are? I'm

Re: type error formatting

On 24 Oct 2015, at 09:17, Joachim Breitner wrote: > For example in > >>Relevant bindings include >> syllables :: [(a1, Syllable)] >> (bound at Derive/Call/India/Pakhawaj.hs:141:16) >> best_match :: [(a1, Syllable)] >> -> Maybe (Int, ([(a1, Syllable)],

Re: type error formatting

Hi, Am Samstag, den 24.10.2015, 10:08 +0100 schrieb Malcolm Wallace: > On 24 Oct 2015, at 09:17, Joachim Breitner wrote: > > > For example in > > > > >    Relevant bindings include > > >   syllables :: [(a1, Syllable)] > > > (bound at Derive/Call/India/Pakhawaj.hs:141:16) > > >  

Re: type error formatting

Hi, thanks for starting this discussion, and I agree with your suggestion. Maybe we can brainstorm some more fine refinements. Given that our error message are on the rather verbose side, maybe there is detail that can be omitted. For example in >    Relevant bindings include >       syllables

Re: type error formatting

I have the same issue with the current error messages. I think these are all good ideas. On 10/24/2015 05:48 AM, Evan Laforge wrote: > Here's a typical simple type error from GHC: > > Derive/Call/India/Pakhawaj.hs:142:62: > Couldn't match type ‘Text’ with ‘(a1, Syllable)’ > Expected

Re: type error formatting

I think this is quite a reasonable suggestion. Edward Excerpts from Evan Laforge's message of 2015-10-23 19:48:07 -0700: > Here's a typical simple type error from GHC: > > Derive/Call/India/Pakhawaj.hs:142:62: > Couldn't match type ‘Text’ with ‘(a1, Syllable)’ > Expected type: [([(a1,