rustdoc does not forward lint settings to the doctest builds
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
TIL that while a bunch of flags are forwarded to doctests builds (including --cfg and --check-cfg), this is not true for --cap-lints as well as -A/-D and the other lint flags. This caught me by surprise when I tried to suppress a deny(warnings) in a doctest. See Zulip for the surrounding discussion.
Would it make sense to also forward the lint flags to the test build? That would seem to make things more consistent.
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 tracing how rustdoc forwards --cfg and --check-cfg into doctest builds, then compare that path with --cap-lints and the -A/-D lint flags described in the issue. Review the linked Zulip discussion for context. Done means the relevant lint settings are forwarded consistently and the doctest behavior is covered by validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100