-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Auto merge of #6476 - 1c3t3a:1c3t3a-from-over-into, r=llogiq
Added from_over_into lint Closes #6456 Added a lint that searches for implementations of `Into<..>` and suggests to implement `From<..>` instead, as it comes with a default implementation of `Into`. Category: style.
- Loading branch information
Showing
10 changed files
with
158 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
use crate::utils::paths::INTO; | ||
use crate::utils::{match_def_path, meets_msrv, span_lint_and_help}; | ||
use if_chain::if_chain; | ||
use rustc_hir as hir; | ||
use rustc_lint::{LateContext, LateLintPass, LintContext}; | ||
use rustc_semver::RustcVersion; | ||
use rustc_session::{declare_tool_lint, impl_lint_pass}; | ||
|
||
const FROM_OVER_INTO_MSRV: RustcVersion = RustcVersion::new(1, 41, 0); | ||
|
||
declare_clippy_lint! { | ||
/// **What it does:** Searches for implementations of the `Into<..>` trait and suggests to implement `From<..>` instead. | ||
/// | ||
/// **Why is this bad?** According the std docs implementing `From<..>` is preferred since it gives you `Into<..>` for free where the reverse isn't true. | ||
/// | ||
/// **Known problems:** None. | ||
/// | ||
/// **Example:** | ||
/// | ||
/// ```rust | ||
/// struct StringWrapper(String); | ||
/// | ||
/// impl Into<StringWrapper> for String { | ||
/// fn into(self) -> StringWrapper { | ||
/// StringWrapper(self) | ||
/// } | ||
/// } | ||
/// ``` | ||
/// Use instead: | ||
/// ```rust | ||
/// struct StringWrapper(String); | ||
/// | ||
/// impl From<String> for StringWrapper { | ||
/// fn from(s: String) -> StringWrapper { | ||
/// StringWrapper(s) | ||
/// } | ||
/// } | ||
/// ``` | ||
pub FROM_OVER_INTO, | ||
style, | ||
"Warns on implementations of `Into<..>` to use `From<..>`" | ||
} | ||
|
||
pub struct FromOverInto { | ||
msrv: Option<RustcVersion>, | ||
} | ||
|
||
impl FromOverInto { | ||
#[must_use] | ||
pub fn new(msrv: Option<RustcVersion>) -> Self { | ||
FromOverInto { msrv } | ||
} | ||
} | ||
|
||
impl_lint_pass!(FromOverInto => [FROM_OVER_INTO]); | ||
|
||
impl LateLintPass<'_> for FromOverInto { | ||
fn check_item(&mut self, cx: &LateContext<'tcx>, item: &'tcx hir::Item<'_>) { | ||
if !meets_msrv(self.msrv.as_ref(), &FROM_OVER_INTO_MSRV) { | ||
return; | ||
} | ||
|
||
let impl_def_id = cx.tcx.hir().local_def_id(item.hir_id); | ||
if_chain! { | ||
if let hir::ItemKind::Impl{ .. } = &item.kind; | ||
if let Some(impl_trait_ref) = cx.tcx.impl_trait_ref(impl_def_id); | ||
if match_def_path(cx, impl_trait_ref.def_id, &INTO); | ||
|
||
then { | ||
span_lint_and_help( | ||
cx, | ||
FROM_OVER_INTO, | ||
item.span, | ||
"an implementation of `From` is preferred since it gives you `Into<_>` for free where the reverse isn't true", | ||
None, | ||
"consider to implement `From` instead", | ||
); | ||
} | ||
} | ||
} | ||
|
||
extract_msrv_attr!(LateContext); | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
#![warn(clippy::from_over_into)] | ||
|
||
// this should throw an error | ||
struct StringWrapper(String); | ||
|
||
impl Into<StringWrapper> for String { | ||
fn into(self) -> StringWrapper { | ||
StringWrapper(self) | ||
} | ||
} | ||
|
||
// this is fine | ||
struct A(String); | ||
|
||
impl From<String> for A { | ||
fn from(s: String) -> A { | ||
A(s) | ||
} | ||
} | ||
|
||
fn main() {} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
error: An implementation of `From` is preferred since it gives you `Into<_>` for free where the reverse isn't true. | ||
--> $DIR/from_over_into.rs:6:1 | ||
| | ||
LL | / impl Into<StringWrapper> for String { | ||
LL | | fn into(self) -> StringWrapper { | ||
LL | | StringWrapper(self) | ||
LL | | } | ||
LL | | } | ||
| |_^ | ||
| | ||
= note: `-D clippy::from-over-into` implied by `-D warnings` | ||
= help: consider to implement `From` instead | ||
|
||
error: aborting due to previous error | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters