summaryrefslogtreecommitdiff
path: root/compiler/utils/Outputable.lhs
diff options
context:
space:
mode:
authorIan Lynagh <igloo@earth.li>2012-06-14 16:24:32 +0100
committerIan Lynagh <igloo@earth.li>2012-06-14 16:24:32 +0100
commit956911e4ae9f58550fd5b86c8a0b0b2590e6e3eb (patch)
treec7215dcc10a893ed6cceb8344fc93e9728ae9471 /compiler/utils/Outputable.lhs
parent46c184e101092c53e9675bcfcb90cf06e513368d (diff)
downloadhaskell-956911e4ae9f58550fd5b86c8a0b0b2590e6e3eb.tar.gz
Be strict in the DynFlags inside an SDoc
This is safe now that the tracingDynFlags is not just a call to panic. Not sure if it was causing a problem as it was, but this change should help make sure we don't get a chain of thunks built up inside SDocs.
Diffstat (limited to 'compiler/utils/Outputable.lhs')
-rw-r--r--compiler/utils/Outputable.lhs2
1 files changed, 1 insertions, 1 deletions
diff --git a/compiler/utils/Outputable.lhs b/compiler/utils/Outputable.lhs
index b2ad099009..cbe4f846b6 100644
--- a/compiler/utils/Outputable.lhs
+++ b/compiler/utils/Outputable.lhs
@@ -238,7 +238,7 @@ data SDocContext = SDC
{ sdocStyle :: !PprStyle
, sdocLastColour :: !PprColour
-- ^ The most recently used colour. This allows nesting colours.
- , sdocDynFlags :: DynFlags
+ , sdocDynFlags :: !DynFlags
}
initSDocContext :: DynFlags -> PprStyle -> SDocContext