You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
use winnow::{prelude::*, token::any};fnmain(){let tokens = [Token];let result = my_parser.parse(&mut tokens.as_slice());let err = result.unwrap_err();let stream = err.input();let _offset = &stream[err.offset()];}/* The stream is a vec of custom tokens. */typeTokenSlice<'slice,'input> = &'slicemut&'input[Token];#[derive(Debug,Clone)]pubstructToken;pubfnmy_parser(i:TokenSlice) -> PResult<()>{
any.verify(|_| false).parse_next(i)?;Ok(())}
Steps to reproduce the bug with the above code
cargo run
Actual Behaviour
thread 'main' panicked at /Users/adamchalmers/.cargo/registry/src/index.crates.io-6f17d22bba15001f/winnow-0.5.16/src/stream/mod.rs:1306:9:
attempt to divide by zero
Expected Behaviour
Report the correct offset (in this case, index 0)
Additional Context
Zero-sized types are a weird edge case and I don't expect this to actually come up. I found this bug while trying to minimize my reproduction for #341. I'd personally consider this a low-priority bug.
The text was updated successfully, but these errors were encountered:
* New parser built with Winnow
This new parser uses [winnow](docs.rs/winnow) to replace the handwritten recursive parser.
## Differences
I think the Winnow parser is more readable than handwritten one, due to reusing standard combinators. If you have a parsre like `p` or `q` you can combine them with standard functions like `repeat(0..4, p)`, `opt(p)`, `alt((p, q))` and `separated1(p, ", ")`. This IMO makes it more readable once you know what those standard functions do.
It's also more accurate now -- e.g. the parser no longer swallows whitespace between comments, or inserts it where there was none before. It no longer changes // comments to /* comments depending on the surrounding whitespace.
Primary form of testing was running the same KCL program through both the old and new parsers and asserting that both parsers produce the same AST. See the test `parser::parser_impl::tests::check_parsers_work_the_same`. But occasionally the new and old parsers disagree. This is either:
- Innocuous (e.g. disagreeing on whether a comment starts at the preceding whitespace or at the //)
- Helpful (e.g. new parser recognizes comments more accurately, preserving the difference between // and /* comments)
- Acceptably bad (e.g. new parser sometimes outputs worse error messages, TODO in #784)
so those KCL programs have their own unit tests in `parser_impl.rs` demonstrating the behaviour.
If you'd like to review this PR, it's arguably more important to review changes to the existing unit tests rather than the new parser itself. Because changes to the unit tests show where my parser changes behaviour -- usually for the better, occasionally for the worse (e.g. a worse error message than before). I think overall the improvements are worth it that I'd like to merge it without spending another week fixing it up -- we can fix the error messages in a follow-up PR.
## Performance
| Benchmark | Old parser (this branch) | New parser (this branch) | Speedup |
| ------------- | ------------- | ------------- | ------------- |
| Pipes on pipes | 922 ms | 42 ms | 21x |
| Kitt SVG | 148 ms | 7 ms | 21x |
There's definitely still room to improve performance:
- #839
- #840
## Winnow
Y'all know I love [Nom](docs.rs/nom) and I've blogged about it a lot. But I'm very happy using Winnow, a fork. It's got some really nice usability improvements. While writing this PR I found some bugs or unclear docs in Winnow:
- winnow-rs/winnow#339
- winnow-rs/winnow#341
- winnow-rs/winnow#342
- winnow-rs/winnow#344
The maintainer was quick to close them and release new versions within a few hours, so I feel very confident building the parser on this library. It's a clear improvement over Nom and it's used in toml-edit (and therefore within Cargo) and Gitoxide, so it's becoming a staple of the Rust ecosystem, which adds confidence.
Closes#716Closes#815Closes#599
Please complete the following tasks
rust version
1.72.1
winnow version
0.5.16
Minimal reproducible code
Steps to reproduce the bug with the above code
cargo run
Actual Behaviour
thread 'main' panicked at /Users/adamchalmers/.cargo/registry/src/index.crates.io-6f17d22bba15001f/winnow-0.5.16/src/stream/mod.rs:1306:9:
attempt to divide by zero
Expected Behaviour
Report the correct offset (in this case, index 0)
Additional Context
Zero-sized types are a weird edge case and I don't expect this to actually come up. I found this bug while trying to minimize my reproduction for #341. I'd personally consider this a low-priority bug.
The text was updated successfully, but these errors were encountered: