-
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
Unify lints handling in rustdoc #71581
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this is tidier, I think I'd benefit from a bit of documentation on the purpose and meaning of the arguments to, and results of, the init_lints()
function. I appreciate the behaviour doesn't appear to have changed, but that doesn't mean I understand it.
Good point, thanks for bringing it up! I'll document the function to make it as clear as possible. |
3ef43a5
to
9ae85e1
Compare
I added more documentation to explain what's going on. |
That doc helps me understand a good bit better, thanks. @bors r+ |
📌 Commit 9ae85e1 has been approved by |
Rollup of 6 pull requests Successful merges: - rust-lang#71581 (Unify lints handling in rustdoc) - rust-lang#71710 (Test for zero-sized function items not ICEing) - rust-lang#71970 (Improve bitcode generation for Apple platforms) - rust-lang#71975 (Reduce `TypedArena` creations in `check_match`.) - rust-lang#72003 (allow wasm target for rustc-ap-rustc_span) - rust-lang#72017 (Work around ICEs during cross-compilation for target, ast, & attr) Failed merges: r? @ghost
This is a small cleanup. The goal is to unify a bit things to make the reading simpler.
r? @kinnison
cc @rust-lang/rustdoc