about summary refs log tree commit diff
path: root/compiler/rustc_mir_transform/src/coverage/graph.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2021-11-25 13:11:35 +0000
committerbors <bors@rust-lang.org>2021-11-25 13:11:35 +0000
commit862962b90e59c5c1e217df74de80d3a81eee42f4 (patch)
treed08084e3f7768bf07dc8047752f6314416ba353d /compiler/rustc_mir_transform/src/coverage/graph.rs
parent23a436606b118bd2fbb12f64fce21e7f9d355349 (diff)
parent617bbb21f8a4f92a234b1e36d276f1a13b3411ce (diff)
downloadrust-862962b90e59c5c1e217df74de80d3a81eee42f4.tar.gz
rust-862962b90e59c5c1e217df74de80d3a81eee42f4.zip
Auto merge of #91195 - camelid:path-did, r=jyn514
rustdoc: Remove `ResolvedPath.did`

`ResolvedPath.did` was not actually the same as `.path.def_id()`. Instead,
`.did` referred to the `DefId` of the page to be used as a hyperlink target.
For example, a link to `Struct::method()` would use `Struct`'s `DefId` as its
`.did` field. This behavior is confusing, easy to accidentally misuse, and can
instead be obtained on-demand when computing hyperlink targets. It's also likely
part of the reason `kind_side_channel` exists. I'm currently working on some
experimental refactorings in `collect_intra_doc_links` that I believe require --
or at least benefit from -- removing `.did`.

r? `@jyn514`
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/graph.rs')
0 files changed, 0 insertions, 0 deletions