Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependents of Specific Items In a Crate #3542

Open
amab8901 opened this issue Dec 12, 2023 · 0 comments
Open

Dependents of Specific Items In a Crate #3542

amab8901 opened this issue Dec 12, 2023 · 0 comments

Comments

@amab8901
Copy link

Current situation:
We are able to see a list of dependents of an entire crate via crates.io. We're also able to see minimalistic examples in the documentation of the item of interest.

Suggestion:
Add a feature that allows you to see the dependents of a specific item within a crate (rather than the entire crate).

Purpose:
Makes it easier to find existing implementation examples of the given item, so that the user can easily and conveniently learn how to correctly implement the item and make it work. The implementation examples would show the item's interaction with other code parts in a complex (and thus realistic) environment - which the minimalistic code examples in the item's documentation don't communicate.

Example:
https://docs.rs/axum/0.7.2/axum/struct.Extension.html
This struct has only minimalistic usage examples. But how would it look like in a larger context when it interacts with other code parts in a complex project? In order for me to find out, I'd have to go through all the dependents of the axum crate, go to their Github, and ctrl+F for Extension until I find a project that uses this item. This can be quite time-consuming. The proposed feature above should make this search for implementation examples more straightforward so that Rust crates in general will become easier to work with

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant