From 232a483331242a3c10097b0c182c80b1403b7a1e Mon Sep 17 00:00:00 2001 From: Michael Rutter Date: Sun, 28 Oct 2018 12:31:02 +0000 Subject: [PATCH] more consistent use of terminology; trait > syntax --- clippy_lints/src/methods/mod.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/clippy_lints/src/methods/mod.rs b/clippy_lints/src/methods/mod.rs index 8e3a75f2c7b..10e6644b70e 100644 --- a/clippy_lints/src/methods/mod.rs +++ b/clippy_lints/src/methods/mod.rs @@ -569,13 +569,13 @@ declare_clippy_lint! { /// concise. /// /// **Known problems:** Not a replacement for error handling: Using either -/// `.unwrap()` or the Index syntax (`[]`) carries the risk of causing a `panic` +/// `.unwrap()` or the Index trait (`[]`) carries the risk of causing a `panic` /// if the value being accessed is `None`. If the use of `.get().unwrap()` is a /// temporary placeholder for dealing with the `Option` type, then this does /// not mitigate the need for error handling. If there is a chance that `.get()` /// will be `None` in your program, then it is advisable that the `None` case -/// is eventually handled in a future refactor instead of using `.unwrap()` -/// or the Index syntax. +/// is handled in a future refactor instead of using `.unwrap()` or the Index +/// trait. /// /// **Example:** /// ```rust