summaryrefslogtreecommitdiff
path: root/libraries/ghc-compact/GHC/Compact.hs
diff options
context:
space:
mode:
Diffstat (limited to 'libraries/ghc-compact/GHC/Compact.hs')
-rw-r--r--libraries/ghc-compact/GHC/Compact.hs4
1 files changed, 2 insertions, 2 deletions
diff --git a/libraries/ghc-compact/GHC/Compact.hs b/libraries/ghc-compact/GHC/Compact.hs
index e3efaf24bc..d9581a521e 100644
--- a/libraries/ghc-compact/GHC/Compact.hs
+++ b/libraries/ghc-compact/GHC/Compact.hs
@@ -30,7 +30,7 @@
-- dump the memory to disk and/or send it over the network.
-- For applications that are not bandwidth bound (GHC's heap
-- representation can be as much of a x4 expansion over a
--- binary serialization), this can lead to substantial speed ups.
+-- binary serialization), this can lead to substantial speedups.
--
-- For example, suppose you have a function @loadBigStruct :: IO BigStruct@,
-- which loads a large data structure from the file system. You can "compact"
@@ -106,7 +106,7 @@ import GHC.Types
-- data, but it is perfomed only once. However, because
-- "Data.Compact.compact" does not stop-the-world, retaining internal
-- sharing during the compaction process is very costly. The user
--- can choose wether to 'compact' or 'compactWithSharing'.
+-- can choose whether to 'compact' or 'compactWithSharing'.
--
-- When you have a @'Compact' a@, you can get a pointer to the actual object
-- in the region using "Data.Compact.getCompact". The 'Compact' type