[GHC] #12963: Give -fexpose-all-unfoldings the same semantics as INLINABLE on each function

[GHC]

#12963: Give -fexpose-all-unfoldings the same semantics as INLINABLE on each
function
-------------------------------------+-------------------------------------
        Reporter:  MikolajKonarski   |                Owner:
            Type:  feature request   |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Compiler          |              Version:  8.0.1
      Resolution:                    |             Keywords:  Inlining
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:  #12962 #12463     |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------
Changes (by MikolajKonarski):

 * related:  #12962 => #12962 #12463


Comment:

 Yes, I'm being lazy. I've only benchmarked my big codebase
 (https://github.com/LambdaHack/LambdaHack). It may not be easy to find a
 small example in which GHC nevertheless fails to specialize a function for
 which it has an available unfolding.

 I got the bit about `INLINABLE` forcing specialization from here:
 https://ghc.haskell.org/trac/ghc/ticket/12463#comment:8

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