From 7428e2d1349fe03da821ee2181ccf7395b9cfe30 Mon Sep 17 00:00:00 2001 From: Camelid Date: Tue, 5 Jan 2021 19:46:51 -0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Joshua Nelson --- src/librustdoc/clean/types.rs | 2 +- src/librustdoc/core.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/librustdoc/clean/types.rs b/src/librustdoc/clean/types.rs index 0364bfd5951f..38791fcea548 100644 --- a/src/librustdoc/clean/types.rs +++ b/src/librustdoc/clean/types.rs @@ -293,7 +293,7 @@ impl Item { /// See the documentation for [`next_def_id()`]. /// - /// [`next_def_id()`]: crate::core::DocContext::next_def_id() + /// [`next_def_id()`]: DocContext::next_def_id() crate fn is_fake(&self) -> bool { MAX_DEF_ID.with(|m| { m.borrow().get(&self.def_id.krate).map(|id| self.def_id >= *id).unwrap_or(false) diff --git a/src/librustdoc/core.rs b/src/librustdoc/core.rs index ac3b8895996b..43aaefa08707 100644 --- a/src/librustdoc/core.rs +++ b/src/librustdoc/core.rs @@ -123,7 +123,7 @@ impl<'tcx> DocContext<'tcx> { /// Create a new "fake" [`DefId`]. /// /// This is an ugly hack, but it's the simplest way to handle synthetic impls without greatly - /// refactoring either `librustdoc` or [`rustc_middle`]. In particular, allowing new [`DefId`]s + /// refactoring either rustdoc or [`rustc_middle`]. In particular, allowing new [`DefId`]s /// to be registered after the AST is constructed would require storing the [`DefId`] mapping /// in a [`RefCell`], decreasing the performance for normal compilation for very little gain. ///