space spaceChar lineComment blockComment produces 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).

spaceChar is used to parse trivial space characters. You can use spaceChar from Text.Megaparsec.Char for this purpose as well as your own parser (if you don't want to automatically consume newlines, for example).

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 if you don't need anything special.

Parsing of white space is an important part of any parser. We propose a convention where every lexeme parser assumes no spaces before the lexeme and consumes all spaces after the lexeme; this is what the lexeme combinator does, and so it's enough to wrap every lexeme parser with lexeme to achieve this. Note that you'll need to call space manually to consume any white space before the first lexeme (i.e. at the beginning of the file).

This is a wrapper for lexemes. Typical usage is to supply the first argument (parser that consumes white space, probably defined via space) and use the resulting function to wrap parsers for every lexeme.

lexeme  = L.lexeme spaceConsumer
integer = lexeme L.integer

This is a helper to parse symbols, i.e. verbatim strings. You pass the first argument (parser that consumes white space, probably defined via space) and then you can use the resulting function to parse strings:

symbol    = L.symbol spaceConsumer

parens    = between (symbol "(") (symbol ")")
braces    = between (symbol "{") (symbol "}")
angles    = between (symbol "<") (symbol ">")
brackets  = between (symbol "[") (symbol "]")
semicolon = symbol ";"
comma     = symbol ","
colon     = symbol ":"
dot       = symbol "."

Case-insensitive version of symbol. This may be helpful if you're working with case-insensitive languages.

Given comment prefix this function returns a parser that skips line comments. Note that it stops just before 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: 5.0.0

Return current indentation level.

The function is a simple shortcut defined as:

indentLevel = sourceColumn <$> getPosition

Since: 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: 5.0.0

indentGuard spaceConsumer ord ref first consumes all white space (indentation) with spaceConsumer parser, then it checks 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 (unsafePos 1) — 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 non-indented construction. This ensures that there is no indentation before actual data. Useful, for example, as a wrapper for top-level function definitions.

Since: 4.3.0

The data type represents available behaviors for parsing of indented tokens. This is used in indentBlock, which see.

Since: 4.3.0

Parse a “reference” token and a number of other tokens that have greater (but the same) level of indentation than that of “reference” token. Reference token can influence parsing, see IndentOpt for more information.

Tokens must not consume newlines after them. On the other hand, the first argument of this function must consume newlines among other white space characters.

Since: 4.3.0

Create a parser that supports line-folding. The first argument is used to consume white space between components of line fold, thus it must consume newlines in order to work properly. The second argument is a callback that receives custom space-consuming parser as argument. This parser should be used after separate components of line fold that can be put on different lines.

An example should clarify the usage pattern:

sc = L.space (void spaceChar) empty empty

myFold = L.lineFold sc $ \sc' -> do
  L.symbol sc' "foo"
  L.symbol sc' "bar"
  L.symbol sc  "baz" -- for the last symbol we use normal space consumer

Since: 5.0.0

The lexeme parser parses a single literal character without quotes. 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 '"')

If you want to write stringLiteral that adheres to the Haskell report though, you'll need to take care of the \& combination which is not a character, but can be used to separate characters (as in "\291\&4" which is two characters long):

stringLiteral = catMaybes <$> (char '"' >> manyTill ch (char '"'))
  where ch = (Just <$> L.charLiteral) <|> (Nothing <$ string "\\&")

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

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

The same as integer, but integer is labeled with “integer” label, while this parser is labeled with “decimal integer”.

Parse an integer in hexadecimal representation. Representation of 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 responsibility of the programmer to parse correct prefix before parsing the number itself.

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

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

Parse an integer in octal representation. Representation of 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 responsibility of the programmer to parse correct prefix before parsing the number itself.

Parse a floating point value as Scientific number. Scientific is great for parsing of arbitrary precision numbers coming from an untrusted source. See documentation in Data.Scientific for more information. Representation of the floating point value is expected to be according to the Haskell report.

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

Since: 5.0.0

Parse a floating point number without sign. This is a simple shortcut defined as:

float = toRealFloat <$> scientific

Parse a number: either integer or floating point. The parser can handle overlapping grammars graciously. Use functions like floatingOrInteger from Data.Scientific to test and extract integer or real values.

signed space p parser parses an optional sign, then if there is a sign it will consume optional white space (using space parser), then it runs parser p which should return a number. Sign of the number is changed according to previously parsed sign.

For example, to parse signed integer you can write:

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