Remove non-informative phrases from docs

Parsec's legacy.
This commit is contained in:
mrkkrp 2016-01-22 13:00:58 +06:00
parent c2f5504725
commit 24b8e41af0

View File

@ -43,15 +43,7 @@ import Data.Foldable (foldMap)
import Data.Monoid import Data.Monoid
#endif #endif
-- | This data type represents parse error messages. There are three kinds -- | This data type represents parse error messages.
-- of messages:
--
-- > data Message = Unexpected String
-- > | Expected String
-- > | Message String
--
-- The fine distinction between different kinds of parse errors allows the
-- system to generate quite good error messages for the user.
data Message data Message
= Unexpected !String -- ^ Parser ran into an unexpected token = Unexpected !String -- ^ Parser ran into an unexpected token
@ -86,9 +78,7 @@ badMessage = null . messageString
-- | The data type @ParseError@ represents parse errors. It provides the -- | The data type @ParseError@ represents parse errors. It provides the
-- source position ('SourcePos') of the error and a list of error messages -- source position ('SourcePos') of the error and a list of error messages
-- ('Message'). A @ParseError@ can be returned by the function -- ('Message').
-- 'Text.Parsec.Prim.parse'. @ParseError@ is an instance of the 'Show' and
-- 'Eq' type classes.
data ParseError = ParseError data ParseError = ParseError
{ -- | Extract the source position from 'ParseError'. { -- | Extract the source position from 'ParseError'.