29 Mar
2018
29 Mar
'18
11:26 a.m.
"Victor Miraldo (UU)"
Dear ghc-devs,
We are working on a library and came across quite high memory consumption when compiling some code (generated by TH).
This memory issue seems to come from the exhaustiveness checker as we found in: https://ghc.haskell.org/trac/ghc/ticket/11163 https://ghc.haskell.org/trac/ghc/ticket/11195
We came up with a "minimal" example that at least is self contained and triggers the problem; `runghc Minimal.hs` should finish with about 5GB of RAM.
Hmm, with 8.2 I'm seeing a peak memory usage of 3.5 GB, with that peak occurring during renaming, not desugaring (when exhaustiveness checking happens). Are you certain that the exhaustiveness checker is the responsible party? Cheers, - Ben