regression: reached recursion limit
Open
Nobody has claimed this yet.
P-medium
regression-from-stable-to-stable
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
- https://crater-reports.s3.amazonaws.com/beta-1.79-2/beta-2024-05-11/gh/jwiegley.motoko_parse/log.txt
[INFO] [stdout] error: reached the recursion limit while instantiating `<(&mut combine::parser::sequence::Skip<combine::parser::combinator::Try<combine::parser::error::Expected<..., ...>>, ...>, ..., ...) as Parser<...>>::parse_mode::<...>`
[INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/combine-4.6.2/src/parser/combinator.rs:236:15
[INFO] [stdout] |
[INFO] [stdout] 236 | match self.0.parse_mode(mode, input, state) {
[INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Crater log and identify the reported Rust compiler version and failing Motoko parser case. Inspect the referenced combine-4.6.2 parser/combinator.rs:236:15 context, then look for a reproducible test case for the recursion-limit regression. Done means the failure is reproduced and its compiler impact or fix is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100