[GHC] #16302: A non-function coerced to a function can cause a stg_ap_v_ret

[GHC]

#16302: A non-function coerced to a function can cause a stg_ap_v_ret
-------------------------------------+-------------------------------------
        Reporter:  WheatWizard       |                Owner:  (none)
            Type:  bug               |               Status:  closed
        Priority:  normal            |            Milestone:
       Component:  Compiler          |              Version:  8.4.3
      Resolution:  invalid           |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:  x86_64
                                     |  (amd64)
 Type of failure:  Runtime crash     |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:  #11826            |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------
Changes (by RyanGlScott):

 * status:  new => closed
 * resolution:   => invalid
 * related:   => #11826


Comment:

 Indeed, once you start using `unsafeCoerce` in a cavalier fashion like
 this, you're taking your own life into your hands. The fact that it
 happened to produce a panic is sheer coincidence—it might have done
 something even stranger, like segfault.

 For the reasons explained in #11826 and comment:1, I'm going to mark this
 as not-a-bug unless there's a compelling reason to believe otherwise.

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