universally directly depend on serde_derive instead of accessing it through serde.
Open
Nobody has claimed this yet.
C-cleanup
T-bootstrap
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
bootstrap does this in order to flatten its dependencies and improve build times, but since other crates (like compiletest and rustdoc) use the derive feature flag, i believe this means serde has to be built twice to use any of these programs.
wouldn't it be best to always use the same set of feature flags to serde?
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 bootstrap dependency setup and compare how compiletest and rustdoc use serde's derive feature. Trace whether these components build separate serde copies, then verify that the dependency declarations use a consistent serde and serde_derive configuration without worsening build behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100