ghc-4.04 + large constant defs = *BOOM*.

[Alex Ferguson]

I've observed before that ghc is a tad sluggish and hungry on modules
with large data defs within, but ghc-4.04 seems especially thus;  on a
1500-ish length list of 10-tuples, I need somewhere north of 200M
of heap to compile in, on a Solaris2.5 machine.  I can ameliorate this
a fair bit by chopping up the definition, but that seems a rather brutal
solution.  Any reason why it's so bad?  (Example furnishable on request,
if this isn't considered a Known Feature.)

Cheers,
Alex.