#12357: Increasing maximum constraint tuple size significantly blows up compiler allocations -------------------------------------+------------------------------------- Reporter: bgamari | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.10.3 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Compile-time | Unknown/Multiple performance bug | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Phab:D2400 Wiki Page: | -------------------------------------+------------------------------------- Comment (by simonpj): OK, you are right. Let's NOT wire-in the rep-names. That would be bad. I recant on comment:27. Lesser evil is to add the rep-names of boxed tuples (but still not the tuple tycons or data cons) to the known-key names, and otherwise not treat them specially. Unboxed and constratint tuples (and uncoming unboxed sums) remain un- representable, but that's a problem for another day. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12357#comment:33 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler