#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: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: #12962 | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by mpickering): This is very vague. You say that the semantics are different but how have you observed this? `INLINABLE` doesn't do anything about "forcing specialisation" so I'm unclear what you mean. If I was to guess I would say that `-fexpose-all-unfoldings` exposes optimised unfoldings rather than unoptimised unfoldings like `INLINABLE`. Now to make progress, do you have a small code sample which behaves differently with `INLINABLE` vs `-fexpose-all-unfoldings`? -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12963#comment:2 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler