Uh oh!
There was an error while loading. Please reload this page.
rustdoc: Fix resolution of crate-relative paths in doc links - #95337
Conversation
rust-highfive
commented
Mar 26, 2022
r? @estebank (rust-highfive has picked a reviewer for you, use r? to override) |
petrochenkov
commented
Mar 26, 2022
camelid
left a comment
There was a problem hiding this comment.
Thanks for this refactoring! It looks very good overall; I just have a few questions.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
petrochenkov
commented
Mar 28, 2022
Updated. |
This comment was marked as resolved.
This comment was marked as resolved.
petrochenkov
commented
Apr 4, 2022
ping @camelid |
camelid
left a comment
There was a problem hiding this comment.
Sorry for the delay, I got busy.
camelid
commented
Apr 4, 2022
@bors r+ rollup=never (may affect perf) |
bors
commented
Apr 4, 2022
📌 Commit f5ee822 has been approved by |
bors
commented
Apr 5, 2022
bors
commented
Apr 5, 2022
☀️ Test successful - checks-actions |
rust-timer
commented
Apr 5, 2022
Finished benchmarking commit (949b98c): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
rylev
commented
Apr 5, 2022
@petrochenkov@camelid this broke one of the perf benchmarks. You can see the error if you click of the perf comparison url and look at the "Newly broken benchmarks" section. I've pasted the error below. Looks like the this PR caused this unreachable code to be reached. Details``` expected success, got exit status: 101stderr= Documenting hyper v0.14.18 (/tmp/.tmpR27TDg) thread 'rustc' panicked at 'internal error: entered unreachable code', compiler/rustc_resolve/src/lib.rs:3302:67 error: internal compiler error: unexpected panic note: the compiler unexpectedly panicked. this is a bug. note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md note: rustc 1.62.0-nightly (949b98c 2022-04-05) running on x86_64-unknown-linux-gnu note: compiler flags: --crate-type lib -Z incremental -Z self-profile=/tmp/.tmpR27TDg/self-profile-output note: some of the compiler flags provided by cargo are hidden query stack during panic: Caused by: stdout=6460071822;;instructions:u;1249486087;100.00;1.44;insn per cycle;; |
petrochenkov
commented
Apr 5, 2022
@rylev |
petrochenkov
commented
Apr 5, 2022
Fixed in #95681. |
resolve: Fix resolution of empty paths passed from rustdoc Fixesrust-lang#95337 (comment)
resolve: Fix resolution of empty paths passed from rustdoc Fixesrust-lang#95337 (comment)
Resolve
crate::foopaths transparently to rustdoc, so their resolution no longer affects diagnostics and modules used for determining traits in scope.The proper solution is to account for the current
module_id/parent_scopeinfn resolve_crate_root, but it's a slightly larger compiler changes. This PR moves the code closer to it, but keeps it rustdoc-specific.Fixes#78696
Fixes#94924