#2168: ghci should show haddock comments for identifier
-----------------------------+----------------------------------------------
 Reporter:  j.waldmann       |          Owner:         
     Type:  feature request  |         Status:  new    
 Priority:  normal           |      Milestone:         
Component:  GHCi             |        Version:  6.8.2  
 Severity:  normal           |     Resolution:         
 Keywords:                   |     Difficulty:  Unknown
 Testcase:                   |   Architecture:  Unknown
       Os:  Unknown          |  
-----------------------------+----------------------------------------------
Changes (by igloo):

  * difficulty:  => Unknown

Old description:

> This came up in comp.lang.haskell recently:
> http://groups.google.com/group/comp.lang.haskell/msg/ae69f720377e7a3f
>
> I like the idea.
>
> Immediate thoughts:
> * if ghci reads the source file, it can read haddock annotations
> * if ghci reads the interface file only (for library modules),
>   it needs to find the installed documentation
>
> On the other hand the requested feature is a typical IDE functionality
> (cf. Eclipse/show source/show javadoc) and it's perhaps a bit much
> to require that from ghci.

New description:

 This came up in comp.lang.haskell recently:
 http://groups.google.com/group/comp.lang.haskell/msg/ae69f720377e7a3f

 I like the idea.

 Immediate thoughts:
  * if ghci reads the source file, it can read haddock annotations
  * if ghci reads the interface file only (for library modules),
    it needs to find the installed documentation

 On the other hand the requested feature is a typical IDE functionality
 (cf. Eclipse/show source/show javadoc) and it's perhaps a bit much
 to require that from ghci.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2168#comment:1>
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