Newtype wrapper for line space consumer. In common cases you should use standard combinators from Text.Megaparsec.Char.Lexer.New rather than unwrap it manually

A type synonym for space and eol consumer. Should be called manually wherever line break is expected

space sc lineComment blockComment produces a parser that can parse white space in general. It's expected that you create such a parser once and pass it to other functions in this module as needed (when you see spaceConsumer in documentation, usually it means that something like space is expected there).

sc is used to parse blocks of space characters. You can use space1 from Text.Megaparsec.Char for this purpose as well as your own parser (if you don't want to automatically consume newlines, for example). Make sure that the parser does not succeed on the empty input though. In an earlier version of the library spaceChar was recommended, but now parsers based on takeWhile1P are preferred because of their speed.

lineComment is used to parse line comments. You can use skipLineComment if you don't need anything special.

blockComment is used to parse block (multi-line) comments. You can use skipBlockComment or skipBlockCommentNested if you don't need anything special.

If you don't want to allow a kind of comment, simply pass empty which will fail instantly when parsing of that sort of comment is attempted and space will just move on or finish depending on whether there is more white space for it to consume.

A lexeme sc p behaves like p and consumes spaces by sc after it

symbol sc toks parse toks and consumes spaces by sc after them

A case-insensitive version of symbol

Given a comment prefix this function returns a parser that skips line comments. Note that it stops just before the newline character but doesn't consume the newline. Newline is either supposed to be consumed by space parser or picked up manually.

skipBlockComment start end skips non-nested block comment starting with start and ending with end.

skipBlockCommentNested start end skips possibly nested block comment starting with start and ending with end.

Since: megaparsec-5.0.0

Return the current indentation level.

The function is a simple shortcut defined as:

indentLevel = sourceColumn <$> getPosition

Since: megaparsec-4.3.0

Fail reporting incorrect indentation error. The error has attached information:

• Desired ordering between reference level and actual level
• Reference indentation level
• Actual indentation level

Since: megaparsec-5.0.0

indentGuard spaceConsumer ord ref first consumes all white space (indentation) with spaceConsumer parser, then it checks the column position. Ordering between current indentation level and the reference indentation level ref should be ord, otherwise the parser fails. On success the current column position is returned.

When you want to parse a block of indentation, first run this parser with arguments like indentGuard spaceConsumer GT pos1—this will make sure you have some indentation. Use returned value to check indentation on every subsequent line according to syntax of your language.

Parse a block of consecutive lines with the same Indentation

For example, for parsing something like

foo
bar
baz

you can use something like this

block space $ scn -> do
  string "foo" <* scn
  string "bar" <* scn
  string "baz" -- we do not use eol consumer after the last string!

Generalized version of block, providing a way to change what is desired ordering related to a reference indentation level

Parse a head of the block and then its body, depending on what Body is returned after processing of the head. Use it if the choice of body parser depends on the head parser's result. In other cases you should prefer headedOneheadedSomeheadedMany/headedOptional

For example, suppose we want to parse something like this (in the first line we have an arbitrary identifier and than it's repeated in all subsequent lines):

foo:
  foo 42
  foo 36

we can use something like this:

headedBlock space space $ do
  name <- takeWhile1P isLetter
  string ":"
  pure $ someBody (L.symbol hspace name *> L.decimal)

Opaque type, containing information about parsing headedBlocks body

Functor instance can be used to modify a result value

Don't parse anything, just return a constant value. Can be used if after parsing head you realized that there should be no body here

Parse a body by given callback. Callback can use space consumer to parse a multiline body. If the body consists of some identical parts use someBody/manyBody instead.

Note, that it will always fail, if the body is empty, even if a callback can succeed without consuming input. Use optionBody/optionalBody in this case.

Parse a body by given callback, if the next line after a head has greater indentation level, otherwise return a constant value

Parse a body by given callback, if the next line after a head has greater indentation level, otherwise return Nothing

optionalBody = optionBody Nothing

Parse some (greater, than zero) number of lines by given parser

someBody pEl = oneBody (pEl `sepBy1`)

Parse many (maybe zero) lines by given parser

manyBody pEl = optionBody [] (pEl `sepBy`)

The lexeme parser parses a single literal character without quotes. The purpose of this parser is to help with parsing of conventional escape sequences. It's your responsibility to take care of character literal syntax in your language (by surrounding it with single quotes or similar).

The literal character is parsed according to the grammar rules defined in the Haskell report.

Note that you can use this parser as a building block to parse various string literals:

stringLiteral = char '"' >> manyTill L.charLiteral (char '"')

Performance note: the parser is not particularly efficient at the moment.

Parse an integer in the decimal representation according to the format of integer literals described in the Haskell report.

If you need to parse signed integers, see the signed combinator.

Note: before the version 6.0.0 the function returned Integer, i.e. it wasn't polymorphic in its return type.

Parse an integer in binary representation. The binary number is expected to be a non-empty sequence of zeroes “0” and ones “1”.

You could of course parse some prefix before the actual number:

binary = char '0' >> char' 'b' >> L.binary

Since: megaparsec-7.0.0

Parse an integer in the octal representation. The format of the octal number is expected to be according to the Haskell report except for the fact that this parser doesn't parse “0o” or “0O” prefix. It is a responsibility of the programmer to parse correct prefix before parsing the number itself.

For example you can make it conform to the Haskell report like this:

octal = char '0' >> char' 'o' >> L.octal

Note: before version 6.0.0 the function returned Integer, i.e. it wasn't polymorphic in its return type.

Parse an integer in the hexadecimal representation. The format of the hexadecimal number is expected to be according to the Haskell report except for the fact that this parser doesn't parse “0x” or “0X” prefix. It is a responsibility of the programmer to parse correct prefix before parsing the number itself.

For example you can make it conform to the Haskell report like this:

hexadecimal = char '0' >> char' 'x' >> L.hexadecimal

Note: before version 6.0.0 the function returned Integer, i.e. it wasn't polymorphic in its return type.

Parse a floating point value as a Scientific number. Scientific is great for parsing of arbitrary precision numbers coming from an untrusted source. See documentation in Data.Scientific for more information.

The parser can be used to parse integers or floating point values. Use functions like floatingOrInteger from Data.Scientific to test and extract integer or real values.

This function does not parse sign, if you need to parse signed numbers, see signed.

Since: megaparsec-5.0.0

Parse a floating point number according to the syntax for floating point literals described in the Haskell report.

This function does not parse sign, if you need to parse signed numbers, see signed.

Note: before version 6.0.0 the function returned Double, i.e. it wasn't polymorphic in its return type.

Note: in versions 6.0.0–6.1.1 this function accepted plain integers.

signed space p parses an optional sign character (“+” or “-”), then if there is a sign it consumes optional white space (using the space parser), then it runs the parser p which should return a number. Sign of the number is changed according to the previously parsed sign character.

For example, to parse signed integer you can write:

lexeme        = L.lexeme spaceConsumer
integer       = lexeme L.decimal
signedInteger = L.signed spaceConsumer integer