Investigate if some rustdoc tests can use `minicore` and `//@ add-core-stubs`
Open
Nobody has claimed this yet.
A-compiletest
A-test-infra
A-test-infra-minicore
A-testsuite
C-cleanup
E-needs-investigation
T-bootstrap
T-rustdoc
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Some rustdoc tests may be able to use minicore for core stubs instead of having to manually reimplement core stubs (and have to deal with failures when new lang items are added or existing lang items get renamed/removed).
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
Search the rustdoc tests for cases that manually reimplement core stubs, then read how minicore and //@ add-core-stubs are used. Identify tests that can safely switch to those facilities and verify the selected tests still pass without manual stubs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100