You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running crater to see how common that pattern is. The Lint would have to be at most warn-by-default because there are a handful of cases detected that are actually perfectly reasonable (`type` aliases with per-platform `cfg`, or macros) which are now at best half-heartedly handled.
I've detected a handful of cases where we're calling `.into()` unnecessarily in the `rustc` codebase as well, and changed those.
Copy file name to clipboardexpand all lines: compiler/rustc_lint/messages.ftl
+2
Original file line number
Diff line number
Diff line change
@@ -733,6 +733,8 @@ lint_reserved_prefix = prefix `{$prefix}` is unknown
733
733
.label = unknown prefix
734
734
.suggestion = insert whitespace here to avoid this being parsed as a prefix in Rust 2021
735
735
736
+
lint_self_type_conversion = this conversion is useless `{$source}` to `{$target}`
737
+
736
738
lint_shadowed_into_iter =
737
739
this method call resolves to `<&{$target} as IntoIterator>::into_iter` (due to backwards compatibility), but will resolve to `<{$target} as IntoIterator>::into_iter` in Rust {$edition}
738
740
.use_iter_suggestion = use `.iter()` instead of `.into_iter()` to avoid ambiguity
0 commit comments