#8523: blowup in space/time for type checking and object size for high arity tuples -------------------------------------------------+------------------------- Reporter: carter | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.6.3 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Compile-time performance bug | Unknown/Multiple Test Case: | Difficulty: Blocking: | Unknown | Blocked By: | Related Tickets: -------------------------------------------------+------------------------- Comment (by carter): I think it'd be a good idea to understand this blowup. What I think is specially concerning is the increase in object code size, though that will require some exploration. I'd also like to understand why the equality constraints blow up the compile time. Do we need a better / more robust algorithm for handling the constraints. In some sense its a possible denial of service issue hypothetically. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/8523#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler