chumsky icon indicating copy to clipboard operation
chumsky copied to clipboard

Write expressive, high-performance parsers with ease.

Results 110 chumsky issues
Sort by recently updated
recently updated
newest added

## Proposal Split `chumsky` into two crates - something like `chumsky` and `chumsky-core`, where most things are actually defined in core, but `chumsky` is actually a thin wrapper that renders...

The examples all (AFAICS) use `let` to define parsers. But there are use-cases where this isn't convenient: 1. Unit testing - for more complex languages, it's helpful to expose parsers...

documentation

I'm using 1.0.0a4, and I'm returning a `Rich::custom` error from a `try_map`. I was surprised to find an error message like this: ``` multiple errors found at 7..8 ``` That's...

Hi, I've been meaning to try Chumsky for ages and finally got round to reading the tutorial. Mostly makes sense. Then I look at the examples, e.g. `nano_rust.rs` and it's...

documentation

It would be really handy to be able to build a parser as a static item, and this doesn't seem to be precluded by anything obvious so long as we...

enhancement
api

The title essentially explains it; I was trying out the alpha versions with zero-copy and ran into the lack of this, instead having to opt for `.map_slice(...).try_map(...)`. It would be...

enhancement

Hey there! I'm currently working on rewriting my parser to the new `zero-copy` alpha version, but I hit a bit of a stumbling block in my parsers that generate an...

api

I'm working on a parser for a typescript-like language. I initially used nom, but I switched to chumsky because I really like the error generating and the synergy with ariadne....

bug
error-recovery

I noticed that there is activity in the guide section of the repo. Would it please be possible to document the error recovery chapter first? For most other aspects of...

documentation

Currently, `zero-copy` differentiates between `select!` and `select_ref!`: the former selects upon tokens by-value, the other by-ref. The former is required for inputs that do not implement `BorrowInput` (i.e: those from...

api
1.0