-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
[rustdoc] Tracking issue for --show-coverage
#58154
Comments
I have a in-progress branch locally that i haven't pushed with this. The current idea is that you send an additional flag to rustdoc that makes it count items in the crate, and print something like the following instead of generating docs:
The reason it counts trait impls separately is because trait impls can have their own documentation, but if you don't add docs it inherits from the trait's own docs. Right now, the following items are not counted:
There's an outstanding question on whether we can detect whether a trait impl came from a derive macro (e.g. most of the undocumented trait impls in that sample came from I've also got a thing right now where if you pass both the new flag and
...granted, this is very similar to the missing-docs lint, so this may not be completely useful. |
Maybe not but at least it allows to have an easy option to directly get a documentation coverage result. |
Fixed by #58626. |
--show-coverage
Since the feature is unstable, i'm going to reopen this issue to repurpose it as a tracking issue. I want to try adding a JSON output option to it, for ease of automatic checking, and then i'd like to integrate it into bootstrap or our CI if possible. |
Triage: this flag is still unstable. |
I don't have time to write a proper bug ticket for it, but when using EDIT: 4 years later: #129007 |
Could I bump this? I would really love this feature, and it's been a while since there were any updates here. |
What do you mean? EDIT: About the "Could I bump this?" |
I meant "could I refresh the attention of whoever had been working on this." From the comments here, it looks like the effort to stabilize this flag has stalled. I'd offer to help, but I'm pretty new to Rust. |
Ah I see. Well, we need to make an RFC for that. If you're motivated to write it (which needs to describe exactly which item is part of the count etc), I can help. |
Could it be possible for the coverage report to take into account scraped examples (-Zrustdoc-scrape-examples)? |
cc @QuietMisdreavus
The text was updated successfully, but these errors were encountered: