Default cargo features should include doc-default features
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Crate maintainers should be allowed to specify features which are off by default, but enabled by default in docs. This would allow people to compile docs for all of the extra features, while also turning these features off by default for most builds.
Contributor guide
No contributing guide indexed for this repository
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 reading the proposal in this issue and the repository's RFC process. Define how maintainers would mark features as enabled for documentation while keeping them disabled for normal builds, including the expected documentation and build behavior. Done means the behavior is specified clearly enough for an accepted RFC and subsequent implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100