rust-lang / rust-lang/rustdoc-types
Expose required feature information
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 44
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
It would be great to have a list of the required features for a code item exposed. I'm guessing this would be implemented by parsing cfg or cfg_attrs from the attrs and resolving those. It seems like it should be possible since docs.rs has the info available, but I'm not sure how it resolves it.
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 examining how cfg and cfg_attr entries in attrs are represented and how docs.rs obtains the required-feature information. Define the output shape and resolution behavior, then confirm that each code item exposes the expected required feature list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100