[GHC] #13145: Documentation shouldn't call things functions that aren't functions

[GHC]

#13145: Documentation shouldn't call things functions that aren't functions
-------------------------------------+-------------------------------------
        Reporter:  chris-martin      |                Owner:
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  libraries/base    |              Version:  8.0.1
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
 Type of failure:  Documentation     |  Unknown/Multiple
  bug                                |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by chris-martin):

 I'm not concerned with the math so much as making sure that Haskell does
 actually use its own definitions. To the best of my understanding, a
 function in Haskell is defined as a value of the type `a -> b` for some
 `a` and `b`. Is that disputed?

 Looking at the Haskell Report a bit further, it seems like "function" is
 pretty inconsistently used, so I agree the fix for this problem (''if'' it
 is in fact a problem and not just my misunderstanding) should start there
 at the root. Any idea where is the best place to start that conversation?

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/13145#comment:6>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler