about summary refs log tree commit diff
diff options
context:
space:
mode:
authoronur-ozkan <work@onurozkan.dev>2024-10-10 08:33:14 +0300
committeronur-ozkan <work@onurozkan.dev>2024-10-10 10:33:29 +0300
commitde744eafe134a2f0ddde8db1b0d94ec5f8bc1481 (patch)
tree8d706ccde6dc8140be8fde70e81ebf485c300136
parentb27aee9b8b21b367d12b499de29023d429b0ba79 (diff)
downloadrust-de744eafe134a2f0ddde8db1b0d94ec5f8bc1481.tar.gz
rust-de744eafe134a2f0ddde8db1b0d94ec5f8bc1481.zip
update `rustc_borrowck::places_conflict` doc-comment
Signed-off-by: onur-ozkan <work@onurozkan.dev>
-rw-r--r--compiler/rustc_borrowck/src/places_conflict.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/compiler/rustc_borrowck/src/places_conflict.rs b/compiler/rustc_borrowck/src/places_conflict.rs
index 519ba0b9e0c..679e111caa9 100644
--- a/compiler/rustc_borrowck/src/places_conflict.rs
+++ b/compiler/rustc_borrowck/src/places_conflict.rs
@@ -3,7 +3,7 @@
 //! we can prove overlap one way or another. Essentially, we treat `Overlap` as
 //! a monoid and report a conflict if the product ends up not being `Disjoint`.
 //!
-//! At each step, if we didn't run out of borrow or place, we know that our elements
+//! On each step, if we didn't run out of borrow or place, we know that our elements
 //! have the same type, and that they only overlap if they are the identical.
 //!
 //! For example, if we are comparing these: