pest
pest copied to clipboard
The Elegant Parser
Adds two new features to the Pest debugger - A `next` command that single-steps the debugger. Most useful after hitting a breakpoint. - Empty commands repeat the last command (with...
- Fixed debugger argument handling - Expanded debugger behaviour a bit (like being able to continue a bunch of times) - Added support for tracing the productions of a grammar...
Hi, I absolutely love how pest can report errors in a simple manner. I have fixed many bugs within my grammar because of pest's error reports. However sometimes some extra...
I am running `cargo clippy` over `async-graphql` crate which uses pest `v2.7.11`. ```rust warning: almost complete ascii range --> parser/src/parse/generated.rs:2312:29 | 2312 | state.match_range('0'..'9') | ^^^--^^^ | | | help:...
when running the test-suite for pest in Debians build system the test `miette_error` fails like this: ``` thread 'error::tests::miette_error' panicked at src/error.rs:1185:9: assertion `left == right` failed left: " ×...
**Describe the bug** The `pest::parses_to!` macro produces a compiler error when used in test files. Specifically, using the macro at module scope triggers `error: expected item after attributes`, and adding...
**Describe the bug** Pest grammars can cause overflow within Pest itself. Pest previously introduced set_call_limit to limit the total size of expressions, but this doesn't affect program stack depth. That...
Currently Span implements debug in such a way that start and end are separate fields. But I think this would be a better implementation ```rust impl { fn fmt(&self, f:...