-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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: provide option to turn intra-link resolution errors into proper errors #50082
Comments
Or to just add a |
In my head, adding a blanket "deny everything rustdoc emits on its own" comes dangerously close to rustdoc having to manage its own lint system, complete with collecting all their names, adding allow/warn/deny/forbid levels and flags, adding some crate attributes like |
We have already a huge part merged into rustdoc (we needed it for ui tests). So I think at this point that we could just add the missing parts (which shouldn't be too numerous...). |
With the warning having been converted to a full lint, could this issue be considered solved? Do we have command-line flags for allow/warn/deny/forbid yet? |
No we don't. I'll add it as well. |
…isdreavus Add command line lint manipulation in rustdoc Fixes #50082. r? @QuietMisdreavus
When rendering docs for the standard library just now, i noticed some warnings come out of rustdoc. It would be prudent to make these force rustdoc to fail, so they would cause CI to fail. We did something similar during the Markdown transition with a temporary flag,
--deny-rendering-differences
, so i imagine it would work out the same.The text was updated successfully, but these errors were encountered: