Re: [GHC] #2911: Error messages have the wrong qualified names

[GHC]

#2911: Error messages have the wrong qualified names
---+
  Reporter:  igloo |  Owner:  
  Type:  bug   | Status:  closed  
  Priority:  normal|  Milestone:  7.2.1   
 Component:  Compiler  |Version:  6.11
Resolution:  wontfix   |   Keywords:  
Os:  Unknown/Multiple  |   Architecture:  Unknown/Multiple
   Failure:  None/Unknown  | Difficulty:  Unknown 
  Testcase:|  Blockedby:  
  Blocking:|Related:  
---+

Comment(by simonmar):

 See also #5868

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler

___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #2911: Error messages have the wrong qualified names

[GHC]

#2911: Error messages have the wrong qualified names
---+
  Reporter:  igloo |  Owner:  
  Type:  bug   | Status:  closed  
  Priority:  normal|  Milestone:  7.2.1   
 Component:  Compiler  |Version:  6.11
Resolution:  wontfix   |   Keywords:  
  Testcase:|  Blockedby:  
Difficulty:  Unknown   | Os:  Unknown/Multiple
  Blocking:|   Architecture:  Unknown/Multiple
   Failure:  None/Unknown  |  
---+
Changes (by igloo):

  * status:  new => closed
  * resolution:  => wontfix


Comment:

 I'm going to close this as not worth fixing. After all, errors are already
 differently laid out, don't include comments, etc.

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler

___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #2911: Error messages have the wrong qualified names

[GHC]

#2911: Error messages have the wrong qualified names
-+--
Reporter:  igloo |Owner:  
Type:  bug   |   Status:  new 
Priority:  normal|Milestone:  6.14.1  
   Component:  Compiler  |  Version:  6.11
Keywords:|   Difficulty:  Unknown 
  Os:  Unknown/Multiple  | Testcase:  
Architecture:  Unknown/Multiple  |  Failure:  None/Unknown
-+--
Changes (by igloo):

  * priority:  low => normal
  * failure:  => None/Unknown
  * milestone:  6.12.3 => 6.14.1


Comment:

 See also #2245.

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler
___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #2911: Error messages have the wrong qualified names

[GHC]

#2911: Error messages have the wrong qualified names
-+--
Reporter:  igloo |Owner:  
Type:  bug   |   Status:  new 
Priority:  low   |Milestone:  6.12 branch 
   Component:  Compiler  |  Version:  6.11
Severity:  minor |   Resolution:  
Keywords:|   Difficulty:  Unknown 
Testcase:|   Os:  Unknown/Multiple
Architecture:  Unknown/Multiple  |  
-+--
Changes (by guest):

 * cc: i...@isaac.cedarswampstudios.org (added)

Comment:

 I vote for caring more about source-correct error messages!

 I thought, if it makes compilation slower, maybe we can add a compiler
 flag to turn it on and off -- but I doubt that would actually work to
 preserve the fast case :-)

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #2911: Error messages have the wrong qualified names

[GHC]

#2911: Error messages have the wrong qualified names
-+--
Reporter:  igloo |Owner:  
Type:  bug   |   Status:  new 
Priority:  low   |Milestone:  6.12 branch 
   Component:  Compiler  |  Version:  6.11
Severity:  minor |   Resolution:  
Keywords:|   Difficulty:  Unknown 
Testcase:|   Os:  Unknown/Multiple
Architecture:  Unknown/Multiple  |  
-+--
Changes (by simonmar):

  * priority:  normal => low
  * milestone:  => 6.12 branch

Comment:

 An alternative way to fix it would be to quote the program source text
 verbatim.  We have a supposedly-accurate source span for the error
 message, so it would be possible to extract the actual program text from
 the source file and display that.

 Not that I think it's worthwhile spending a lot of time to get this right,
 mind you.

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #2911: Error messages have the wrong qualified names

[GHC]

#2911: Error messages have the wrong qualified names
-+--
Reporter:  igloo |Owner:  
Type:  bug   |   Status:  new 
Priority:  normal|Milestone:  
   Component:  Compiler  |  Version:  6.11
Severity:  minor |   Resolution:  
Keywords:|   Difficulty:  Unknown 
Testcase:|   Os:  Unknown/Multiple
Architecture:  Unknown/Multiple  |  
-+--
Comment (by claus):

 don't know whether this helps, but there was a similar problem when
 implementing the extended `:browse!` in GHCi (see
 `compiler/ghci/InteractiveUI.hs`, `browseModule`), and I settled for the
 compromise of listing the names and possible import routes separately. So
 in the output of `ghc -e ':browse! *Foo'` for the second example, one
 finds
 {{{
 ..
 -- imported via Data.ByteString.Lazy.Char8, BS
 ..
 empty :: ByteString
 ..
 }}}

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #2911: Error messages have the wrong qualified names

[GHC]

#2911: Error messages have the wrong qualified names
-+--
Reporter:  igloo |Owner:  
Type:  bug   |   Status:  new 
Priority:  normal|Milestone:  
   Component:  Compiler  |  Version:  6.11
Severity:  minor |   Resolution:  
Keywords:|   Difficulty:  Unknown 
Testcase:|   Os:  Unknown/Multiple
Architecture:  Unknown/Multiple  |  
-+--
Comment (by simonpj):

 This is a tricky one to fix.  In both cases, the error message reports a
 ''valid'' way of referring to `empty`, just not the way that it was
 written in the source program.

 The trouble is that the renamer has replaced the `RdrName` (which is more
 or less just a string) "BS.empty" by the `Name`
 `Data.ByteString.Lazy.empty`, which uniquely identifies the thing referred
 to (regardless of the string used to name it in the source program).  That
 is, the renamer converts `HsExpr RdrName` to `HsExpr Name`.  So the type
 checker doesn't even know exactly how you originally referred to it.

 It'd be possible to retain the original text in the syntax tree, and
 perhaps better to do so.  That is, make the renamer convert `HsExpr
 RdrName` to `HsExpr (RdrName,Name)`.   This'd add a bit of code, and slow
 down every compilation, so I'm not convinced it's worth it.  Let's see
 what others think.

 Simon

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs