Joshua Barretto
Joshua Barretto
I'm glad you like it, your `recursive_n` approach inspired me to come up with the drop closure solution. > It may be worth considering offering the arm without `= `...
I'd be interested in your thoughts on this @Hedgehogo
I would be happy to see `filter_map` introduced, if anybody is interested in working on it. Behaviourally, it's strictly more useful than `select!` since it applies to any parser's output,...
I'm a little confused. When you return an `Err(...)` from `custom`, the error is associated with whatever location the input is currently at. For example, if you parse the string...
> This is not true, simply based on what is written in custom, the error is always located where custom began, even if it contains complex logic where the error...
I mean that returning an error would cause the error to be located at wherever the closure left the input. Although in hindsight, I think that this might not be...
I guess one option is to make `Located` public, but have all of its constructors be private. Have the only ways to construct one to be like so: ```rs let...
This is very strange indeed! I'll try to find some time to look at this in more detail soon.
It's really quite difficult to give a useful answer with this little to go on. Chumsky is broadly designed such that all of the information the compiler's optimiser needs to...
Such a large difference sometimes implies that the parser is structured in such a way that it needs to perform a lot of backtracking, and likely has exponential complexity. `Parser::parse_with_state`...