#1841: Data.Typeable: Instances of basic types don't provide qualified strings 
to
mkTyCon
----------------------------+-----------------------------------------------
 Reporter:  guest           |          Owner:         
     Type:  bug             |         Status:  new    
 Priority:  normal          |      Milestone:         
Component:  libraries/base  |        Version:  6.8.1  
 Severity:  normal          |     Resolution:         
 Keywords:                  |     Difficulty:  Unknown
 Testcase:                  |   Architecture:  Unknown
       Os:  Unknown         |  
----------------------------+-----------------------------------------------
Changes (by simonpj):

  * difficulty:  => Unknown

Comment:

 All true.  Particularly the point about tuples being "(,,)" etc.

 Whoever wrote `Data.Typeable` didn't think about this I guess.  However
 while it "might be wise" to us a fully-qualified name, a data type like
 `Int` is actually `GHC.Base.Int` for GHC, and doubtless something
 different for Hugs.  So arguably giving the fully-qualified name would
 make life more inconvenient in some ways.  Does it actually ''help'' to
 fully-qualify the names of built-in types like `Int`?

 To put it another way, can you explain in a bit more detail why making it
 all consistent would help you?  (Other than simply making is more
 consistent, which is a good goal, but at a cost as I remarked above.)

 Regardless, we should fix the "(,,)" thing.

 Simon

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1841#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to