#12747: INLINE vs NOINLINE vs <nothing> give three different results; two would be better -------------------------------------+------------------------------------- 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: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by MikolajKonarski): Actually, a weaker guarantee would still be very useful and may be preferable: the above for functions that are referred to only once and, generalizing, for functions that may be inlined in many places, let <nothing> be equivalent to INLINABLE and a certain set of `inline` and `noinline` at each occurrence of the function. Right now this weaker condition doesn't hold, because the function from the test is referred to only once (taking into account any other inlining). -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12747#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler