Lines Matching refs:parses

60 * A parser that parses nothing and always succeeds is
63 * A parser that parses one character and returns the parsed character as the
105 * If parsing succeeds, it parses the remaining string with the second parser
124 whitespaces after the number. So the following parser parses one number and the
173 parser parses the input using [link repeated `repeated`]`<int_token>` and then
196 This example parses the input, builds the list of numbers and then loops over it
203   [link repeated `repeated`]`<int_token>` here. It parses the input with that
242 it achieves the same result by doing less as well. It parses the input by
359 the value `int_<0>` as this starting value). Then it parses all elements of the
422 because [link foldl_start_with_parser `foldl_start_with_parser`] parses the
423 input ['as long as it can]. It parses the first`int_token` (`11`) and then it
429 The problem is that the parser parses the longest sub-expression starting from
452 parses the example invalid input and how it fails. This can be used for better