Re: Poll: Error message spans

2010-01-15 Thread Thomas Schilling
Additionally, tools based on the GHC API already have this information available and wouldn't be affected either way. -- Push the envelope. Watch it bend. ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org

Re: Poll: Error message spans

2010-01-13 Thread Ian Lynagh
On Mon, Jan 11, 2010 at 10:10:03AM +, Simon Marlow wrote: don't think I've ever wanted to know the endpoint of the expression to which an error message refers, Here's an example where it is useful (arguably due to a poor error message): http://hackage.haskell.org/trac/ghc/ticket/3746

Re: Poll: Error message spans

2010-01-11 Thread Simon Marlow
On 06/01/10 11:35, Ian Lynagh wrote: Currently, when GHC reports an error it only gives a source position, not a source span. For example, with this module: main = print (f (const 'x' 'x') 'y') f xs y = xs ++ [y] you get an error starting: u.hs:1:18: Couldn't match

Re: Poll: Error message spans

2010-01-07 Thread Brent Yorgey
On Wed, Jan 06, 2010 at 09:01:46PM -0800, Alexander Dunlap wrote: On Wed, Jan 6, 2010 at 3:35 AM, Ian Lynagh ig...@earth.li wrote: Would you find the extra information useful, or just noise? i.e. should we show error spans by default? I certainly wouldn't find it distracting, and I

Re: Poll: Error message spans

2010-01-07 Thread Malcolm Wallace
Would you find the extra information useful, or just noise? i.e. should we show error spans by default? I certainly wouldn't find it distracting, and I think it could be quite useful in many cases. I vote for turning it on by default. I agree. +1. It is a feature I have always found useful

Poll: Error message spans

2010-01-06 Thread Ian Lynagh
Hi all, Currently, when GHC reports an error it only gives a source position, not a source span. For example, with this module: main = print (f (const 'x' 'x') 'y') f xs y = xs ++ [y] you get an error starting: u.hs:1:18: Couldn't match expected type `[a]' against inferred

Re: Poll: Error message spans

2010-01-06 Thread Bulat Ziganshin
Hello Ian, Wednesday, January 6, 2010, 2:35:09 PM, you wrote: Would you find the extra information useful, or just noise? i.e. should we show error spans by default? i think it's useful in some cases, and don't add noticeable visual overhead in remaining ones -- Best regards, Bulat

Re: Poll: Error message spans

2010-01-06 Thread Alexander Dunlap
On Wed, Jan 6, 2010 at 3:35 AM, Ian Lynagh ig...@earth.li wrote: Hi all, Currently, when GHC reports an error it only gives a source position, not a source span. For example, with this module:    main = print (f (const 'x' 'x') 'y')    f xs y = xs ++ [y] you get an error starting: