Skip to content

Commit 78036a8

Browse files
committed
Auto merge of #8061 - vallentin:fix-same-name-method-desc, r=flip1995
Fixed same_name_method description Noticed some odd phrasing, while checking out the new release. changelog: none
2 parents 392b0c5 + aec74d2 commit 78036a8

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

clippy_lints/src/same_name_method.rs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ use std::collections::{BTreeMap, BTreeSet};
1111

1212
declare_clippy_lint! {
1313
/// ### What it does
14-
/// It lints if a struct has two method with same time:
14+
/// It lints if a struct has two methods with the same name:
1515
/// one from a trait, another not from trait.
1616
///
1717
/// ### Why is this bad?
@@ -100,7 +100,7 @@ impl<'tcx> LateLintPass<'tcx> for SameNameMethod {
100100
cx,
101101
SAME_NAME_METHOD,
102102
*impl_span,
103-
"method's name is same to an existing method in a trait",
103+
"method's name is the same as an existing method in a trait",
104104
|diag| {
105105
diag.span_note(
106106
trait_method_span,
@@ -139,7 +139,7 @@ impl<'tcx> LateLintPass<'tcx> for SameNameMethod {
139139
cx,
140140
SAME_NAME_METHOD,
141141
impl_span,
142-
"method's name is same to an existing method in a trait",
142+
"method's name is the same as an existing method in a trait",
143143
|diag| {
144144
// TODO should we `span_note` on every trait?
145145
// iterate on trait_spans?

0 commit comments

Comments
 (0)