summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlp Mestanogullari <alp@well-typed.com>2019-09-20 07:41:07 -0400
committerMarge Bot <ben+marge-bot@smart-cactus.org>2019-09-21 23:31:08 -0400
commitfa66e3e5a3a34d1b84c4883d374644079e2ed61f (patch)
tree4aef6dc54970eedcd12454314777ac703dbce5c0
parenta7867c7949b9dad95216ad5f2946be2cafcb860c (diff)
downloadhaskell-fa66e3e5a3a34d1b84c4883d374644079e2ed61f.tar.gz
Fix haddocks for marker events in Debug.Trace
-rw-r--r--libraries/base/Debug/Trace.hs2
1 files changed, 1 insertions, 1 deletions
diff --git a/libraries/base/Debug/Trace.hs b/libraries/base/Debug/Trace.hs
index 8e15416384..cfeefbc0ae 100644
--- a/libraries/base/Debug/Trace.hs
+++ b/libraries/base/Debug/Trace.hs
@@ -275,7 +275,7 @@ traceEventIO msg =
-- When looking at a profile for the execution of a program we often want to
-- be able to mark certain points or phases in the execution and see that
-- visually in the profile.
-
+--
-- For example, a program might have several distinct phases with different
-- performance or resource behaviour in each phase. To properly interpret the
-- profile graph we really want to see when each phase starts and ends.