Float out and full laziness

This is a status page for full laziness, implemented by the float-out transformation.

The relevant modules in GHC are SetLevels and FloatOut.


Use Keyword = FloatOut to ensure that a ticket ends up on these lists.

Open Tickets:

-O introduces space leak
Implement cheap build
float-out causes extra allocation
-ffull-laziness does more harm than good
CAF isn't floated
Don't float out lets in between lambdsa
'GHC.Magic.noinline <var>' should not float out

Closed Tickets:

Full laziness is sometimes a pessimisation
memory leak due to optimisation
-O0 runs in constant space, -O1 and -O2 don't
ForeignPtr leak in ghci
Float out causes major space leak

Last modified 23 months ago Last modified on Dec 8, 2017 10:00:02 AM