Skip to content

Issues: zesterer/chumsky

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
10 Open 10 Closed
10 Open 10 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

or choosing secondary option, over recovered first option 1.0 Features that should be implemented for the 1.0 release error-recovery An issue related to chumsky's error recovery API
#677 opened Oct 7, 2024 by KrosFire
1
just(range) passes the range as output instead of the matched value (1.0.7 alpha) 1.0 Features that should be implemented for the 1.0 release api A problem with the design of an API feature
#674 opened Sep 26, 2024 by 0rvar
2
Tracking: Stable 1.0 1.0 Features that should be implemented for the 1.0 release tracking
#543 opened Oct 10, 2023 by zesterer
5 of 34 tasks
5
Building a stable and extensible parser API (and hiding the rougher implementation details behind sealed traits) 1.0 Features that should be implemented for the 1.0 release api A problem with the design of an API feature help wanted Extra attention is needed interop An issue that affects interoperability with other crates
#354 opened Mar 7, 2023 by zesterer
9
Separate span generation logic out from Input trait into extension traits to simplify core API 1.0 Features that should be implemented for the 1.0 release api A problem with the design of an API feature
#331 opened Mar 5, 2023 by zesterer
Find a way to unify select! and select_ref! 1.0 Features that should be implemented for the 1.0 release api A problem with the design of an API feature
#309 opened Mar 1, 2023 by zesterer
Make recursive detect left recursion with debug assertions are enabled 1.0 Features that should be implemented for the 1.0 release enhancement New feature or request good first issue Good for newcomers
#303 opened Feb 28, 2023 by zesterer
1
Add 'static' analysis passes to zero-copy 1.0 Features that should be implemented for the 1.0 release enhancement New feature or request
#280 opened Feb 16, 2023 by zesterer
3
Recovery logic affects parsing of valid input 1.0 Features that should be implemented for the 1.0 release
#159 opened Jun 13, 2022 by jvanstraten
15
Missing documentation with example of the recovery system 1.0 Features that should be implemented for the 1.0 release error-recovery An issue related to chumsky's error recovery API
#42 opened Dec 5, 2021 by bew
4
ProTip! Follow long discussions with comments:>50.