about summary refs log tree commit diff
diff options
context:
space:
mode:
authornils <48135649+Nilstrieb@users.noreply.github.com>2023-01-11 17:30:58 +0100
committerGitHub <noreply@github.com>2023-01-11 17:30:58 +0100
commit9aeef61820b4cd14b3f4cab601a95b15ced5862e (patch)
tree0d19af73ce4d98d239abf182b4dc07a44dff124f
parent80c535f15ce5f54d53f172e8079ec4463b4b98f4 (diff)
parentcce2f5f7726875d3784988f5e54aae7f4421ba85 (diff)
downloadrust-9aeef61820b4cd14b3f4cab601a95b15ced5862e.tar.gz
rust-9aeef61820b4cd14b3f4cab601a95b15ced5862e.zip
Rollup merge of #106717 - klensy:typo, r=lcnr
fix typo LocalItemId -> ItemLocalId
-rw-r--r--compiler/rustc_hir/src/hir_id.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/compiler/rustc_hir/src/hir_id.rs b/compiler/rustc_hir/src/hir_id.rs
index 3b4add0cf4d..404abe2b068 100644
--- a/compiler/rustc_hir/src/hir_id.rs
+++ b/compiler/rustc_hir/src/hir_id.rs
@@ -148,7 +148,7 @@ rustc_index::newtype_index! {
     /// that is, within a `hir::Item`, `hir::TraitItem`, or `hir::ImplItem`. There is no
     /// guarantee that the numerical value of a given `ItemLocalId` corresponds to
     /// the node's position within the owning item in any way, but there is a
-    /// guarantee that the `LocalItemId`s within an owner occupy a dense range of
+    /// guarantee that the `ItemLocalId`s within an owner occupy a dense range of
     /// integers starting at zero, so a mapping that maps all or most nodes within
     /// an "item-like" to something else can be implemented by a `Vec` instead of a
     /// tree or hash map.
@@ -161,7 +161,7 @@ impl ItemLocalId {
     pub const INVALID: ItemLocalId = ItemLocalId::MAX;
 }
 
-// Safety: Ord is implement as just comparing the LocalItemId's numerical
+// Safety: Ord is implement as just comparing the ItemLocalId's numerical
 // values and these are not changed by (de-)serialization.
 unsafe impl StableOrd for ItemLocalId {}