[GHC] #12357: Increasing maximum constraint tuple size significantly blows up compiler allocations

[GHC]

#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):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by Ben Gamari <ben@…>):

 In [changeset:"6c7c193f376fe3b48992724c12f6ff393dca6528/ghc" 6c7c193/ghc]:
 {{{
 #!CommitTicketReference repository="ghc"
 revision="6c7c193f376fe3b48992724c12f6ff393dca6528"
 DsExpr: Remove usage of concatFS in fingerprintName

 This was the only user of concatFS and really just wants the `String`
 anyways.

 Stumbled upon while looking at #12357.

 Test Plan: Validate

 Reviewers: austin

 Reviewed By: austin

 Subscribers: thomie

 Differential Revision: https://phabricator.haskell.org/D2386
 }}}

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/12357#comment:17>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler