about summary refs log tree commit diff
diff options
context:
space:
mode:
authorYusuke Matsushita <y.skm24t@gmail.com>2019-05-12 09:52:38 +0900
committerGitHub <noreply@github.com>2019-05-12 09:52:38 +0900
commit0fc2cfb66c7de60099386a3cc091e2bbb2b2187a (patch)
tree996a7294a65f6e1ffeb849c100232cf548d3099d
parent5f1924c9922c640108d2225d6b68e69e589b94ae (diff)
downloadrust-0fc2cfb66c7de60099386a3cc091e2bbb2b2187a.tar.gz
rust-0fc2cfb66c7de60099386a3cc091e2bbb2b2187a.zip
Fix minor typos for ItemLocalId
* added comma before 'that is'
* "can be implement" -> "can be implemented"
-rw-r--r--src/librustc/hir/mod.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/librustc/hir/mod.rs b/src/librustc/hir/mod.rs
index 9f7fa6c5557..3778324f01a 100644
--- a/src/librustc/hir/mod.rs
+++ b/src/librustc/hir/mod.rs
@@ -126,12 +126,12 @@ mod item_local_id_inner {
     use rustc_macros::HashStable;
     newtype_index! {
         /// An `ItemLocalId` uniquely identifies something within a given "item-like",
-        /// that is within a hir::Item, hir::TraitItem, or hir::ImplItem. There is no
+        /// 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
         /// integers starting at zero, so a mapping that maps all or most nodes within
-        /// an "item-like" to something else can be implement by a `Vec` instead of a
+        /// an "item-like" to something else can be implemented by a `Vec` instead of a
         /// tree or hash map.
         pub struct ItemLocalId {
             derive [HashStable]