#13336: Improve or remove the glomming warning -------------------------------------+------------------------------------- Reporter: mpickering | Owner: (none) Type: task | Status: new Priority: low | 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 simonpj):
GHC dutifully warns us about this event but I can't work out why it this is necessary
The actionable bit (not yet actioned!) is to examine cases where glomming happens a lot, and check that it is actually necessary. They may all be legit, but I know from experience that I make mistakes; perhaps there is an easy win lurking here.
What is bad about glomming?
Two small things: first, the program is optimised without all the relevant bindings visible; second, we build a giant Rec and re-analyse it, which can't be cheap. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/13336#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler