-
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: Cleanup doc link resolution #96345
Conversation
r? @notriddle (rust-highfive has picked a reviewer for you, use r? to override) |
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.
This is really awesome ❤️ thanks!
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.
Overall, these changes seem pretty good, though, admittedly, I'm not an expert on most of this code.
r? jyn514
Try rolling the dice for a different reviewer who knows this code better? r? rust-lang/rustdoc |
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.
r? jyn514
This change looks good to me.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
It's a bug and not an error
in favor of `PreprocessingError::MalformedGenerics`
The variant resolution check didn't make sense, and derive trait collision could be processed in a different way
and otherwise unify resolution in macro namespace and other namespaces
This simplifies error types and allows to remove `fn resolve_inner` and `fn check_full_res` `visited_links` caching is not touched for now
@notriddle I don't think any current team member knows this code better than you, except maybe @camelid. |
This all seems correct to me. I especially like that it reduces the number of LoC overall! I tried building some of the crates that regressed on crater to make sure the macro_rules fallback still works. It seemed to work. @bors r+ |
📌 Commit 9ba5281 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2d69117): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
See individual commits for specific changes