bd38aa1 · typeable/attoparsec

git.iko.soy/typeable/attoparsec

Merge

commitbd38aa15e6d6b7f3f7ee3dc39e8a5a8b86acda75 authorBryan O'Sullivan <bos@serpentine.com> dateFri 24 Aug 2012, 19:13 (14 years ago) parentfdcad23 d793b93

2 files changed+4−4

compare with master

unifiedsplit

Data/Attoparsec/ByteString/Internal.hs+2−2 Data/Attoparsec/Text/Internal.hs+2−2

Data/Attoparsec/ByteString/Internal.hs+2−2

@@ -215,11 +215,11 @@ take n = takeWith n (const True)

215215-- /Note/: The behaviour of this parser is different to that of the

216216-- similarly-named parser in Parsec, as this one is all-or-nothing.

217217-- To illustrate the difference, the following parser will fail under

218−-- Parsec given an input of @"for"@:

218+-- Parsec given an input of @\"for\"@:

219219--

220220-- >string "foo" <|> string "for"

221221--

222−-- The reason for its failure is that that the first branch is a

222+-- The reason for its failure is that the first branch is a

223223-- partial match, and will consume the letters @\'f\'@ and @\'o\'@

224224-- before failing. In Attoparsec, the above parser will /succeed/ on

225225-- that input, because the failed first branch will consume nothing.

Data/Attoparsec/Text/Internal.hs+2−2

@@ -213,11 +213,11 @@ take n = takeWith n (const True)

213213-- /Note/: The behaviour of this parser is different to that of the

214214-- similarly-named parser in Parsec, as this one is all-or-nothing.

215215-- To illustrate the difference, the following parser will fail under

216−-- Parsec given an input of @"for"@:

216+-- Parsec given an input of @\"for\"@:

217217--

218218-- >string "foo" <|> string "for"

219219--

220−-- The reason for its failure is that that the first branch is a

220+-- The reason for its failure is that the first branch is a

221221-- partial match, and will consume the letters @\'f\'@ and @\'o\'@

222222-- before failing. In Attoparsec, the above parser will /succeed/ on

223223-- that input, because the failed first branch will consume nothing.