about summary refs log tree commit diff
diff options
context:
space:
mode:
authorGuillaume Gomez <guillaume1.gomez@gmail.com>2021-05-25 13:05:15 +0200
committerGitHub <noreply@github.com>2021-05-25 13:05:15 +0200
commit46615598a9e7c9ac05f20bcf65ceab5eeba981eb (patch)
treeb0809e934f5d04d707d4382bc46b9dbef8802343
parent0f3c98ad51a37d30cfbd09ba1a4de3dc79b7bfb5 (diff)
parent54ccf95af25143cb3c52d8814c91ac1bc9f1f3c5 (diff)
downloadrust-46615598a9e7c9ac05f20bcf65ceab5eeba981eb.tar.gz
rust-46615598a9e7c9ac05f20bcf65ceab5eeba981eb.zip
Rollup merge of #85644 - tialaramex:master, r=dtolnay
Better English for documenting when to use unimplemented!()

I don't think "plan of using" is correct here. I considered "plan on using" but eventually decided "plan to use" is better.
-rw-r--r--library/core/src/macros/mod.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/core/src/macros/mod.rs b/library/core/src/macros/mod.rs
index b46a7aa138c..feadf5b4c7c 100644
--- a/library/core/src/macros/mod.rs
+++ b/library/core/src/macros/mod.rs
@@ -595,7 +595,7 @@ macro_rules! unreachable {
 /// Indicates unimplemented code by panicking with a message of "not implemented".
 ///
 /// This allows your code to type-check, which is useful if you are prototyping or
-/// implementing a trait that requires multiple methods which you don't plan of using all of.
+/// implementing a trait that requires multiple methods which you don't plan to use all of.
 ///
 /// The difference between `unimplemented!` and [`todo!`] is that while `todo!`
 /// conveys an intent of implementing the functionality later and the message is "not yet