Repository : ssh://[email protected]/containers On branch : ghc-head Link : http://git.haskell.org/?p=packages/containers.git;a=commit;h=0f616f472f5b279713da2935571b773927f13d2d
>--------------------------------------------------------------- commit 0f616f472f5b279713da2935571b773927f13d2d Author: Johan Tibell <[email protected]> Date: Wed Aug 1 16:22:31 2012 -0700 Fix haddock links to modules >--------------------------------------------------------------- 0f616f472f5b279713da2935571b773927f13d2d Data/IntMap/Lazy.hs | 2 +- Data/IntMap/Strict.hs | 4 ++-- Data/Map/Lazy.hs | 2 +- Data/Map/Strict.hs | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/Data/IntMap/Lazy.hs b/Data/IntMap/Lazy.hs index 7e735a9..455308e 100644 --- a/Data/IntMap/Lazy.hs +++ b/Data/IntMap/Lazy.hs @@ -16,7 +16,7 @@ -- (dictionaries). -- -- API of this module is strict in the keys, but lazy in the values. --- If you need value-strict maps, use 'Data.IntMap.Strict' instead. +-- If you need value-strict maps, use "Data.IntMap.Strict" instead. -- The 'IntMap' type itself is shared between the lazy and strict modules, -- meaning that the same 'IntMap' value can be passed to functions in -- both modules (although that is rarely needed). diff --git a/Data/IntMap/Strict.hs b/Data/IntMap/Strict.hs index db472da..b338df1 100644 --- a/Data/IntMap/Strict.hs +++ b/Data/IntMap/Strict.hs @@ -16,7 +16,7 @@ -- (dictionaries). -- -- API of this module is strict in both the keys and the values. --- If you need value-lazy maps, use 'Data.IntMap.Lazy' instead. +-- If you need value-lazy maps, use "Data.IntMap.Lazy" instead. -- The 'IntMap' type itself is shared between the lazy and strict modules, -- meaning that the same 'IntMap' value can be passed to functions in -- both modules (although that is rarely needed). @@ -49,7 +49,7 @@ -- (32 or 64). -- -- Be aware that the 'Functor', 'Traversable' and 'Data' instances --- are the same as for the 'Data.IntMap.Lazy' module, so if they are used +-- are the same as for the "Data.IntMap.Lazy" module, so if they are used -- on strict maps, the resulting maps will be lazy. ----------------------------------------------------------------------------- diff --git a/Data/Map/Lazy.hs b/Data/Map/Lazy.hs index ddccffd..df09cd6 100644 --- a/Data/Map/Lazy.hs +++ b/Data/Map/Lazy.hs @@ -16,7 +16,7 @@ -- (dictionaries). -- -- API of this module is strict in the keys, but lazy in the values. --- If you need value-strict maps, use 'Data.Map.Strict' instead. +-- If you need value-strict maps, use "Data.Map.Strict" instead. -- The 'Map' type itself is shared between the lazy and strict modules, -- meaning that the same 'Map' value can be passed to functions in -- both modules (although that is rarely needed). diff --git a/Data/Map/Strict.hs b/Data/Map/Strict.hs index 82b9bda..5e2912d 100644 --- a/Data/Map/Strict.hs +++ b/Data/Map/Strict.hs @@ -16,7 +16,7 @@ -- (dictionaries). -- -- API of this module is strict in both the keys and the values. --- If you need value-lazy maps, use 'Data.Map.Lazy' instead. +-- If you need value-lazy maps, use "Data.Map.Lazy" instead. -- The 'Map' type is shared between the lazy and strict modules, -- meaning that the same 'Map' value can be passed to functions in -- both modules (although that is rarely needed). @@ -45,7 +45,7 @@ -- the Big-O notation (<http://en.wikipedia.org/wiki/Big_O_notation>). -- -- Be aware that the 'Functor', 'Traversable' and 'Data' instances --- are the same as for the 'Data.Map.Lazy' module, so if they are used +-- are the same as for the "Data.Map.Lazy" module, so if they are used -- on strict maps, the resulting maps will be lazy. ----------------------------------------------------------------------------- _______________________________________________ ghc-commits mailing list [email protected] http://www.haskell.org/mailman/listinfo/ghc-commits
