0.7
Added
-
A new tutorial to help new users
-
select
macro, a wrapper overfilter_map
that makes extracting data from specific tokens easy -
choice
parser, a better alternative to longor
chains (which sometimes have poor compilation performance) -
todo
parser, that panics when used (but not when created) (akin to Rust'stodo!
macro, but for parsers) -
keyword
parser, that parses exact identifiers -
from_str
combinator to allow converting a pattern to a value inline, usingstd::str::FromStr
-
unwrapped
combinator, to automatically unwrap an output value inline -
rewind
combinator, that allows reverting the input stream on success. It's most useful when requiring that a
pattern is followed by some terminating pattern without the first parser greedily consuming it -
map_err_with_span
combinator, to allow fetching the span of the input that was parsed by a parser before an error
was encountered -
or_else
combinator, to allow processing and potentially recovering from a parser error -
SeparatedBy::at_most
to require that a separated pattern appear at most a specific number of times -
SeparatedBy::exactly
to require that a separated pattern be repeated exactly a specific number of times -
Repeated::exactly
to require that a pattern be repeated exactly a specific number of times -
More trait implementations for various things, making the crate more useful
Changed
- Made
just
,one_of
, andnone_of
significant more useful. They can now accept strings, arrays, slices, vectors,
sets, or just single tokens as before - Added the return type of each parser to its documentation
- More explicit documentation of parser behaviour
- More doc examples
- Deprecated
seq
(just
has been generalised and can now be used to parse specific input sequences) - Sealed the
Character
trait so that future changes are not breaking - Sealed the
Chain
trait and made it more powerful - Moved trait constraints on
Parser
to where clauses for improved readability
Fixed
- Fixed a subtle bug that allowed
separated_by
to parse an extra trailing separator when it shouldn't - Filled a 'hole' in the
Error
trait's API that conflated a lack of expected tokens with expectation of end of input - Made recursive parsers use weak reference-counting to avoid memory leaks