ghc-trace-events 0.1.2 → 0.1.2.1

raw patch · 5 files changed

+5/−28 lines, 5 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• CHANGELOG.md +4/−0
• ghc-trace-events.cabal +1/−1
• src/Debug/Trace/ByteString.hs +0/−9
• src/Debug/Trace/String.hs +0/−9
• src/Debug/Trace/Text.hs +0/−9

@@ -1,5 +1,9 @@ # Revision history for ghc-trace-events +## v0.1.2.1 - 2020-06-09++* Delete some haddock comments that are not applicable to this library+ ## v0.1.2 - 2020-06-09  * Revert "Use unsafeUseAsCString in place of useAsCString in Debug.Trace.Text" because it's unsafe

@@ -1,6 +1,6 @@ cabal-version: 2.2 name: ghc-trace-events-version: 0.1.2+version: 0.1.2.1 synopsis: Faster traceEvent and traceMarker, and binary object logging for   eventlog description: ghc-trace-events provides faster traceEvent and traceMarker as well

@@ -37,10 +37,6 @@ -- extra events into the eventlog. In combination with eventlog profiling -- tools these functions can be used for monitoring execution and -- investigating performance problems.------ Currently only GHC provides eventlog profiling, see the GHC user guide for--- details on how to use it. These function exists for other Haskell--- implementations but no events are emitted.  -- | 'B.ByteString' variant of 'Debug.Trace.traceEvent'. --@@ -136,11 +132,6 @@ -- -- Markers let us do this: we can annotate the program to emit a marker at -- an appropriate point during execution and then see that in a profile.------ Currently this feature is only supported in GHC by the eventlog tracing--- system, but in future it may also be supported by the heap profiling or--- other profiling tools. These function exists for other Haskell--- implementations but they have no effect.  -- | 'B.ByteString' variant of 'Debug.Trace.traceMarker'. --

@@ -24,10 +24,6 @@ -- extra events into the eventlog. In combination with eventlog profiling -- tools these functions can be used for monitoring execution and -- investigating performance problems.------ Currently only GHC provides eventlog profiling, see the GHC user guide for--- details on how to use it. These function exists for other Haskell--- implementations but no events are emitted.  -- | Drop-in replacement for 'Debug.Trace.traceEvent' but is more efficient -- if user tracing in eventlog is disabled.@@ -65,11 +61,6 @@ -- -- Markers let us do this: we can annotate the program to emit a marker at -- an appropriate point during execution and then see that in a profile.------ Currently this feature is only supported in GHC by the eventlog tracing--- system, but in future it may also be supported by the heap profiling or--- other profiling tools. These function exists for other Haskell--- implementations but they have no effect.  -- | Drop-in replacement for 'Debug.Trace.traceMarker' but is more efficient -- if user tracing in eventlog is disabled.

@@ -32,10 +32,6 @@ -- extra events into the eventlog. In combination with eventlog profiling -- tools these functions can be used for monitoring execution and -- investigating performance problems.------ Currently only GHC provides eventlog profiling, see the GHC user guide for--- details on how to use it. These function exists for other Haskell--- implementations but no events are emitted.  -- | 'T.Text' variant of 'Debug.Trace.traceEvent'. --@@ -88,11 +84,6 @@ -- -- Markers let us do this: we can annotate the program to emit a marker at -- an appropriate point during execution and then see that in a profile.------ Currently this feature is only supported in GHC by the eventlog tracing--- system, but in future it may also be supported by the heap profiling or--- other profiling tools. These function exists for other Haskell--- implementations but they have no effect.  -- | 'T.Text' variant of 'Debug.Trace.traceMarker'. --