mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Use fragment instead of side channel for prim. assoc. items

Browse Source 
I had the epiphany that now that fragments are "semantic" -- rather than
just strings -- they fill the role that used to be handled by the side
channel. I think I may be able to get rid of the other uses of the side
channel using this technique too.
This commit is contained in:
Noah Lev 2022-01-05 18:12:26 -08:00
parent 7e3132adb3
commit 1064003f8c
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/librustdoc/passes/collect_intra_doc_links.rs
View File

@ -1353,7 +1353,9 @@ impl LinkCollector<'_, '_> {
match res {
Res::Primitive(prim) => {
if let Some((kind, id)) = self.kind_side_channel.take() {
if let Some(UrlFragment::Def(_, id)) = fragment {
let kind = self.cx.tcx.def_kind(id);
// We're actually resolving an associated item of a primitive, so we need to
// verify the disambiguator (if any) matches the type of the associated item.
// This case should really follow the same flow as the `Res::Def` branch below,