1.99 beta crater regression: unresolved import in doctest
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
log: https://crater-reports.s3.amazonaws.com/beta-1.99-5/1.99.0-beta.1/reg/lfchring-0.1.3/log.txt
reduction:
/// ```rust
/// use x::A;
/// ```
#[cfg(any(feature = "a", doc))]
pub struct A;
with Cargo.toml:
[package]
name = "x"
edition = "2024"
[features]
a = []
another instance of this is https://crater-reports.s3.amazonaws.com/beta-1.99-5/1.99.0-beta.1/reg/kolibrios-syscalls-0.2.0/log.txt
and also https://crater-reports.s3.amazonaws.com/beta-1.99-5/1.99.0-beta.1/reg/memory_pages-0.1.0/log.txt
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 by reproducing the minimal Rust crate and doctest shown in the issue, then compare the crater logs for lfchring, kolibrios-syscalls, and memory_pages. Trace the compiler's doctest and cfg handling to identify the regression; done when the documented imports resolve for the reduction and the reported cases.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100