Export crates used in public APIs
Open
enhancement
- Dominant language
- Rust
- Stars
- 4.8k
- Forks
- 565
- PR merge metrics
- No merged PRs in 30d
Description
This is something I've run into many times. For example, I sometimes need to add an explicit dependency on `num` or `num_traits` in order to use `num::Zero` in generic contexts.
This issue is a reminder for us to go through the public API and export all crates that appear.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue identifies the public API and `num`/`num_traits` as starting points. Audit exposed types and signatures for crates that users must currently depend on directly, then verify the completed API no longer requires those extra dependencies. Done means all crates appearing in the public API are exported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100