1 //! Some lints that are built in to the compiler.
3 //! These are the built-in lints that are emitted direct in the main
4 //! compiler code, rather than using their own custom pass. Those
5 //! lints are all available in `rustc_lint::builtin`.
7 use crate::{declare_lint, declare_lint_pass, FutureIncompatibilityReason};
8 use rustc_span::edition::Edition;
9 use rustc_span::symbol::sym;
12 /// The `forbidden_lint_groups` lint detects violations of
13 /// `forbid` applied to a lint group. Due to a bug in the compiler,
14 /// these used to be overlooked entirely. They now generate a warning.
19 /// #![forbid(warnings)]
20 /// #![deny(bad_style)]
27 /// ### Recommended fix
29 /// If your crate is using `#![forbid(warnings)]`,
30 /// we recommend that you change to `#![deny(warnings)]`.
34 /// Due to a compiler bug, applying `forbid` to lint groups
35 /// previously had no effect. The bug is now fixed but instead of
36 /// enforcing `forbid` we issue this future-compatibility warning
37 /// to avoid breaking existing crates.
38 pub FORBIDDEN_LINT_GROUPS,
40 "applying forbid to lint-groups",
41 @future_incompatible = FutureIncompatibleInfo {
42 reference: "issue #81670 <https://github.com/rust-lang/rust/issues/81670>",
47 /// The `ill_formed_attribute_input` lint detects ill-formed attribute
48 /// inputs that were previously accepted and used in practice.
52 /// ```rust,compile_fail
53 /// #[inline = "this is not valid"]
61 /// Previously, inputs for many built-in attributes weren't validated and
62 /// nonsensical attribute inputs were accepted. After validation was
63 /// added, it was determined that some existing projects made use of these
64 /// invalid forms. This is a [future-incompatible] lint to transition this
65 /// to a hard error in the future. See [issue #57571] for more details.
67 /// Check the [attribute reference] for details on the valid inputs for
70 /// [issue #57571]: https://github.com/rust-lang/rust/issues/57571
71 /// [attribute reference]: https://doc.rust-lang.org/nightly/reference/attributes.html
72 /// [future-incompatible]: ../index.md#future-incompatible-lints
73 pub ILL_FORMED_ATTRIBUTE_INPUT,
75 "ill-formed attribute inputs that were previously accepted and used in practice",
76 @future_incompatible = FutureIncompatibleInfo {
77 reference: "issue #57571 <https://github.com/rust-lang/rust/issues/57571>",
83 /// The `conflicting_repr_hints` lint detects [`repr` attributes] with
84 /// conflicting hints.
86 /// [`repr` attributes]: https://doc.rust-lang.org/reference/type-layout.html#representations
90 /// ```rust,compile_fail
101 /// The compiler incorrectly accepted these conflicting representations in
102 /// the past. This is a [future-incompatible] lint to transition this to a
103 /// hard error in the future. See [issue #68585] for more details.
105 /// To correct the issue, remove one of the conflicting hints.
107 /// [issue #68585]: https://github.com/rust-lang/rust/issues/68585
108 /// [future-incompatible]: ../index.md#future-incompatible-lints
109 pub CONFLICTING_REPR_HINTS,
111 "conflicts between `#[repr(..)]` hints that were previously accepted and used in practice",
112 @future_incompatible = FutureIncompatibleInfo {
113 reference: "issue #68585 <https://github.com/rust-lang/rust/issues/68585>",
118 /// The `meta_variable_misuse` lint detects possible meta-variable misuse
119 /// in macro definitions.
123 /// ```rust,compile_fail
124 /// #![deny(meta_variable_misuse)]
126 /// macro_rules! foo {
128 /// ($( $i:ident = $($j:ident),+ );*) => { $( $( $i = $k; )+ )* };
140 /// There are quite a few different ways a [`macro_rules`] macro can be
141 /// improperly defined. Many of these errors were previously only detected
142 /// when the macro was expanded or not at all. This lint is an attempt to
143 /// catch some of these problems when the macro is *defined*.
145 /// This lint is "allow" by default because it may have false positives
146 /// and other issues. See [issue #61053] for more details.
148 /// [`macro_rules`]: https://doc.rust-lang.org/reference/macros-by-example.html
149 /// [issue #61053]: https://github.com/rust-lang/rust/issues/61053
150 pub META_VARIABLE_MISUSE,
152 "possible meta-variable misuse at macro definition"
156 /// The `incomplete_include` lint detects the use of the [`include!`]
157 /// macro with a file that contains more than one expression.
159 /// [`include!`]: https://doc.rust-lang.org/std/macro.include.html
163 /// ```rust,ignore (needs separate file)
165 /// include!("foo.txt");
169 /// where the file `foo.txt` contains:
178 /// error: include macro expected single expression in source
181 /// 1 | println!("1");
184 /// = note: `#[deny(incomplete_include)]` on by default
189 /// The [`include!`] macro is currently only intended to be used to
190 /// include a single [expression] or multiple [items]. Historically it
191 /// would ignore any contents after the first expression, but that can be
192 /// confusing. In the example above, the `println!` expression ends just
193 /// before the semicolon, making the semicolon "extra" information that is
194 /// ignored. Perhaps even more surprising, if the included file had
195 /// multiple print statements, the subsequent ones would be ignored!
197 /// One workaround is to place the contents in braces to create a [block
198 /// expression]. Also consider alternatives, like using functions to
199 /// encapsulate the expressions, or use [proc-macros].
201 /// This is a lint instead of a hard error because existing projects were
202 /// found to hit this error. To be cautious, it is a lint for now. The
203 /// future semantics of the `include!` macro are also uncertain, see
206 /// [items]: https://doc.rust-lang.org/reference/items.html
207 /// [expression]: https://doc.rust-lang.org/reference/expressions.html
208 /// [block expression]: https://doc.rust-lang.org/reference/expressions/block-expr.html
209 /// [proc-macros]: https://doc.rust-lang.org/reference/procedural-macros.html
210 /// [issue #35560]: https://github.com/rust-lang/rust/issues/35560
211 pub INCOMPLETE_INCLUDE,
213 "trailing content in included file"
217 /// The `arithmetic_overflow` lint detects that an arithmetic operation
220 /// [overflow]: https://doc.rust-lang.org/reference/expressions/operator-expr.html#overflow
224 /// ```rust,compile_fail
232 /// It is very likely a mistake to perform an arithmetic operation that
233 /// overflows its value. If the compiler is able to detect these kinds of
234 /// overflows at compile-time, it will trigger this lint. Consider
235 /// adjusting the expression to avoid overflow, or use a data type that
236 /// will not overflow.
237 pub ARITHMETIC_OVERFLOW,
239 "arithmetic operation overflows"
243 /// The `unconditional_panic` lint detects an operation that will cause a
244 /// panic at runtime.
248 /// ```rust,compile_fail
249 /// # #![allow(unused)]
257 /// This lint detects code that is very likely incorrect because it will
258 /// always panic, such as division by zero and out-of-bounds array
259 /// accesses. Consider adjusting your code if this is a bug, or using the
260 /// `panic!` or `unreachable!` macro instead in case the panic is intended.
261 pub UNCONDITIONAL_PANIC,
263 "operation will cause a panic at runtime"
267 /// The `const_err` lint detects an erroneous expression while doing
268 /// constant evaluation.
272 /// ```rust,compile_fail
273 /// #![allow(unconditional_panic)]
274 /// const C: i32 = 1/0;
281 /// This lint detects constants that fail to evaluate. Allowing the lint will accept the
282 /// constant declaration, but any use of this constant will still lead to a hard error. This is
283 /// a future incompatibility lint; the plan is to eventually entirely forbid even declaring
284 /// constants that cannot be evaluated. See [issue #71800] for more details.
286 /// [issue #71800]: https://github.com/rust-lang/rust/issues/71800
289 "constant evaluation encountered erroneous expression",
290 @future_incompatible = FutureIncompatibleInfo {
291 reference: "issue #71800 <https://github.com/rust-lang/rust/issues/71800>",
292 reason: FutureIncompatibilityReason::FutureReleaseErrorReportNow,
294 report_in_external_macro
298 /// The `unused_imports` lint detects imports that are never used.
303 /// use std::collections::HashMap;
310 /// Unused imports may signal a mistake or unfinished code, and clutter
311 /// the code, and should be removed. If you intended to re-export the item
312 /// to make it available outside of the module, add a visibility modifier
316 "imports that are never used"
320 /// The `must_not_suspend` lint guards against values that shouldn't be held across suspend points
326 /// #![feature(must_not_suspend)]
327 /// #![warn(must_not_suspend)]
329 /// #[must_not_suspend]
330 /// struct SyncThing {}
332 /// async fn yield_now() {}
334 /// pub async fn uhoh() {
335 /// let guard = SyncThing {};
336 /// yield_now().await;
344 /// The `must_not_suspend` lint detects values that are marked with the `#[must_not_suspend]`
345 /// attribute being held across suspend points. A "suspend" point is usually a `.await` in an async
348 /// This attribute can be used to mark values that are semantically incorrect across suspends
349 /// (like certain types of timers), values that have async alternatives, and values that
350 /// regularly cause problems with the `Send`-ness of async fn's returned futures (like
353 pub MUST_NOT_SUSPEND,
355 "use of a `#[must_not_suspend]` value across a yield point",
356 @feature_gate = rustc_span::symbol::sym::must_not_suspend;
360 /// The `unused_extern_crates` lint guards against `extern crate` items
361 /// that are never used.
365 /// ```rust,compile_fail
366 /// #![deny(unused_extern_crates)]
367 /// extern crate proc_macro;
374 /// `extern crate` items that are unused have no effect and should be
375 /// removed. Note that there are some cases where specifying an `extern
376 /// crate` is desired for the side effect of ensuring the given crate is
377 /// linked, even though it is not otherwise directly referenced. The lint
378 /// can be silenced by aliasing the crate to an underscore, such as
379 /// `extern crate foo as _`. Also note that it is no longer idiomatic to
380 /// use `extern crate` in the [2018 edition], as extern crates are now
381 /// automatically added in scope.
383 /// This lint is "allow" by default because it can be noisy, and produce
384 /// false-positives. If a dependency is being removed from a project, it
385 /// is recommended to remove it from the build configuration (such as
386 /// `Cargo.toml`) to ensure stale build entries aren't left behind.
388 /// [2018 edition]: https://doc.rust-lang.org/edition-guide/rust-2018/module-system/path-clarity.html#no-more-extern-crate
389 pub UNUSED_EXTERN_CRATES,
391 "extern crates that are never used"
395 /// The `unused_crate_dependencies` lint detects crate dependencies that
400 /// ```rust,ignore (needs extern crate)
401 /// #![deny(unused_crate_dependencies)]
404 /// This will produce:
407 /// error: external crate `regex` unused in `lint_example`: remove the dependency or add `use regex as _;`
409 /// note: the lint level is defined here
410 /// --> src/lib.rs:1:9
412 /// 1 | #![deny(unused_crate_dependencies)]
413 /// | ^^^^^^^^^^^^^^^^^^^^^^^^^
418 /// After removing the code that uses a dependency, this usually also
419 /// requires removing the dependency from the build configuration.
420 /// However, sometimes that step can be missed, which leads to time wasted
421 /// building dependencies that are no longer used. This lint can be
422 /// enabled to detect dependencies that are never used (more specifically,
423 /// any dependency passed with the `--extern` command-line flag that is
424 /// never referenced via [`use`], [`extern crate`], or in any [path]).
426 /// This lint is "allow" by default because it can provide false positives
427 /// depending on how the build system is configured. For example, when
428 /// using Cargo, a "package" consists of multiple crates (such as a
429 /// library and a binary), but the dependencies are defined for the
430 /// package as a whole. If there is a dependency that is only used in the
431 /// binary, but not the library, then the lint will be incorrectly issued
434 /// [path]: https://doc.rust-lang.org/reference/paths.html
435 /// [`use`]: https://doc.rust-lang.org/reference/items/use-declarations.html
436 /// [`extern crate`]: https://doc.rust-lang.org/reference/items/extern-crates.html
437 pub UNUSED_CRATE_DEPENDENCIES,
439 "crate dependencies that are never used",
444 /// The `unused_qualifications` lint detects unnecessarily qualified
449 /// ```rust,compile_fail
450 /// #![deny(unused_qualifications)]
465 /// If an item from another module is already brought into scope, then
466 /// there is no need to qualify it in this case. You can call `bar()`
467 /// directly, without the `foo::`.
469 /// This lint is "allow" by default because it is somewhat pedantic, and
470 /// doesn't indicate an actual problem, but rather a stylistic choice, and
471 /// can be noisy when refactoring or moving around code.
472 pub UNUSED_QUALIFICATIONS,
474 "detects unnecessarily qualified names"
478 /// The `unknown_lints` lint detects unrecognized lint attributes.
483 /// #![allow(not_a_real_lint)]
490 /// It is usually a mistake to specify a lint that does not exist. Check
491 /// the spelling, and check the lint listing for the correct name. Also
492 /// consider if you are using an old version of the compiler, and the lint
493 /// is only available in a newer version.
496 "unrecognized lint attribute"
500 /// The `unfulfilled_lint_expectations` lint detects lint trigger expectations
501 /// that have not been fulfilled.
506 /// #![feature(lint_reasons)]
508 /// #[expect(unused_variables)]
510 /// println!("{}", x);
517 /// It was expected that the marked code would emit a lint. This expectation
518 /// has not been fulfilled.
520 /// The `expect` attribute can be removed if this is intended behavior otherwise
521 /// it should be investigated why the expected lint is no longer issued.
523 /// In rare cases, the expectation might be emitted at a different location than
524 /// shown in the shown code snippet. In most cases, the `#[expect]` attribute
525 /// works when added to the outer scope. A few lints can only be expected
526 /// on a crate level.
528 /// Part of RFC 2383. The progress is being tracked in [#54503]
530 /// [#54503]: https://github.com/rust-lang/rust/issues/54503
531 pub UNFULFILLED_LINT_EXPECTATIONS,
533 "unfulfilled lint expectation",
534 @feature_gate = rustc_span::sym::lint_reasons;
538 /// The `unused_variables` lint detects variables which are not used in
551 /// Unused variables may signal a mistake or unfinished code. To silence
552 /// the warning for the individual variable, prefix it with an underscore
554 pub UNUSED_VARIABLES,
556 "detect variables which are not used in any way"
560 /// The `unused_assignments` lint detects assignments that will never be read.
573 /// Unused assignments may signal a mistake or unfinished code. If the
574 /// variable is never used after being assigned, then the assignment can
575 /// be removed. Variables with an underscore prefix such as `_x` will not
576 /// trigger this lint.
577 pub UNUSED_ASSIGNMENTS,
579 "detect assignments that will never be read"
583 /// The `dead_code` lint detects unused, unexported items.
595 /// Dead code may signal a mistake or unfinished code. To silence the
596 /// warning for individual items, prefix the name with an underscore such
597 /// as `_foo`. If it was intended to expose the item outside of the crate,
598 /// consider adding a visibility modifier like `pub`. Otherwise consider
599 /// removing the unused code.
602 "detect unused, unexported items"
606 /// The `unused_attributes` lint detects attributes that were not used by
619 /// Unused [attributes] may indicate the attribute is placed in the wrong
620 /// position. Consider removing it, or placing it in the correct position.
621 /// Also consider if you intended to use an _inner attribute_ (with a `!`
622 /// such as `#![allow(unused)]`) which applies to the item the attribute
623 /// is within, or an _outer attribute_ (without a `!` such as
624 /// `#[allow(unused)]`) which applies to the item *following* the
627 /// [attributes]: https://doc.rust-lang.org/reference/attributes.html
628 pub UNUSED_ATTRIBUTES,
630 "detects attributes that were not used by the compiler"
634 /// The `unreachable_code` lint detects unreachable code paths.
639 /// panic!("we never go past here!");
648 /// Unreachable code may signal a mistake or unfinished code. If the code
649 /// is no longer in use, consider removing it.
650 pub UNREACHABLE_CODE,
652 "detects unreachable code paths",
653 report_in_external_macro
657 /// The `unreachable_patterns` lint detects unreachable patterns.
673 /// This usually indicates a mistake in how the patterns are specified or
674 /// ordered. In this example, the `y` pattern will always match, so the
675 /// five is impossible to reach. Remember, match arms match in order, you
676 /// probably wanted to put the `5` case above the `y` case.
677 pub UNREACHABLE_PATTERNS,
679 "detects unreachable patterns"
683 /// The `overlapping_range_endpoints` lint detects `match` arms that have [range patterns] that
684 /// overlap on their endpoints.
686 /// [range patterns]: https://doc.rust-lang.org/nightly/reference/patterns.html#range-patterns
693 /// 0..=100 => { println!("small"); }
694 /// 100..=255 => { println!("large"); }
702 /// It is likely a mistake to have range patterns in a match expression that overlap in this
703 /// way. Check that the beginning and end values are what you expect, and keep in mind that
704 /// with `..=` the left and right bounds are inclusive.
705 pub OVERLAPPING_RANGE_ENDPOINTS,
707 "detects range patterns with overlapping endpoints"
711 /// The `bindings_with_variant_name` lint detects pattern bindings with
712 /// the same name as one of the matched variants.
722 /// pub fn foo(x: Enum) {
734 /// It is usually a mistake to specify an enum variant name as an
735 /// [identifier pattern]. In the example above, the `match` arms are
736 /// specifying a variable name to bind the value of `x` to. The second arm
737 /// is ignored because the first one matches *all* values. The likely
738 /// intent is that the arm was intended to match on the enum variant.
740 /// Two possible solutions are:
742 /// * Specify the enum variant using a [path pattern], such as
744 /// * Bring the enum variants into local scope, such as adding `use
745 /// Enum::*;` to the beginning of the `foo` function in the example
748 /// [identifier pattern]: https://doc.rust-lang.org/reference/patterns.html#identifier-patterns
749 /// [path pattern]: https://doc.rust-lang.org/reference/patterns.html#path-patterns
750 pub BINDINGS_WITH_VARIANT_NAME,
752 "detects pattern bindings with the same name as one of the matched variants"
756 /// The `unused_macros` lint detects macros that were not used.
758 /// Note that this lint is distinct from the `unused_macro_rules` lint,
759 /// which checks for single rules that never match of an otherwise used
760 /// macro, and thus never expand.
765 /// macro_rules! unused {
777 /// Unused macros may signal a mistake or unfinished code. To silence the
778 /// warning for the individual macro, prefix the name with an underscore
779 /// such as `_my_macro`. If you intended to export the macro to make it
780 /// available outside of the crate, use the [`macro_export` attribute].
782 /// [`macro_export` attribute]: https://doc.rust-lang.org/reference/macros-by-example.html#path-based-scope
785 "detects macros that were not used"
789 /// The `unused_macro_rules` lint detects macro rules that were not used.
791 /// Note that the lint is distinct from the `unused_macros` lint, which
792 /// fires if the entire macro is never called, while this lint fires for
793 /// single unused rules of the macro that is otherwise used.
794 /// `unused_macro_rules` fires only if `unused_macros` wouldn't fire.
799 /// #[warn(unused_macro_rules)]
800 /// macro_rules! unused_empty {
801 /// (hello) => { println!("Hello, world!") }; // This rule is unused
802 /// () => { println!("empty") }; // This rule is used
806 /// unused_empty!(hello);
814 /// Unused macro rules may signal a mistake or unfinished code. Furthermore,
815 /// they slow down compilation. Right now, silencing the warning is not
816 /// supported on a single rule level, so you have to add an allow to the
817 /// entire macro definition.
819 /// If you intended to export the macro to make it
820 /// available outside of the crate, use the [`macro_export` attribute].
822 /// [`macro_export` attribute]: https://doc.rust-lang.org/reference/macros-by-example.html#path-based-scope
823 pub UNUSED_MACRO_RULES,
825 "detects macro rules that were not used"
829 /// The `warnings` lint allows you to change the level of other
830 /// lints which produce warnings.
835 /// #![deny(warnings)]
843 /// The `warnings` lint is a bit special; by changing its level, you
844 /// change every other warning that would produce a warning to whatever
845 /// value you'd like. As such, you won't ever trigger this lint in your
849 "mass-change the level for lints which produce warnings"
853 /// The `unused_features` lint detects unused or unknown features found in
854 /// crate-level [`feature` attributes].
856 /// [`feature` attributes]: https://doc.rust-lang.org/nightly/unstable-book/
858 /// Note: This lint is currently not functional, see [issue #44232] for
861 /// [issue #44232]: https://github.com/rust-lang/rust/issues/44232
864 "unused features found in crate-level `#[feature]` directives"
868 /// The `stable_features` lint detects a [`feature` attribute] that
869 /// has since been made stable.
871 /// [`feature` attribute]: https://doc.rust-lang.org/nightly/unstable-book/
876 /// #![feature(test_accepted_feature)]
884 /// When a feature is stabilized, it is no longer necessary to include a
885 /// `#![feature]` attribute for it. To fix, simply remove the
886 /// `#![feature]` attribute.
889 "stable features found in `#[feature]` directive"
893 /// The `unknown_crate_types` lint detects an unknown crate type found in
894 /// a [`crate_type` attribute].
898 /// ```rust,compile_fail
899 /// #![crate_type="lol"]
907 /// An unknown value give to the `crate_type` attribute is almost
908 /// certainly a mistake.
910 /// [`crate_type` attribute]: https://doc.rust-lang.org/reference/linkage.html
911 pub UNKNOWN_CRATE_TYPES,
913 "unknown crate type found in `#[crate_type]` directive",
918 /// The `trivial_casts` lint detects trivial casts which could be replaced
919 /// with coercion, which may require [type ascription] or a temporary
924 /// ```rust,compile_fail
925 /// #![deny(trivial_casts)]
926 /// let x: &u32 = &42;
927 /// let y = x as *const u32;
934 /// A trivial cast is a cast `e as T` where `e` has type `U` and `U` is a
935 /// subtype of `T`. This type of cast is usually unnecessary, as it can be
936 /// usually be inferred.
938 /// This lint is "allow" by default because there are situations, such as
939 /// with FFI interfaces or complex type aliases, where it triggers
940 /// incorrectly, or in situations where it will be more difficult to
941 /// clearly express the intent. It may be possible that this will become a
942 /// warning in the future, possibly with [type ascription] providing a
943 /// convenient way to work around the current issues. See [RFC 401] for
944 /// historical context.
946 /// [type ascription]: https://github.com/rust-lang/rust/issues/23416
947 /// [RFC 401]: https://github.com/rust-lang/rfcs/blob/master/text/0401-coercions.md
950 "detects trivial casts which could be removed"
954 /// The `trivial_numeric_casts` lint detects trivial numeric casts of types
955 /// which could be removed.
959 /// ```rust,compile_fail
960 /// #![deny(trivial_numeric_casts)]
961 /// let x = 42_i32 as i32;
968 /// A trivial numeric cast is a cast of a numeric type to the same numeric
969 /// type. This type of cast is usually unnecessary.
971 /// This lint is "allow" by default because there are situations, such as
972 /// with FFI interfaces or complex type aliases, where it triggers
973 /// incorrectly, or in situations where it will be more difficult to
974 /// clearly express the intent. It may be possible that this will become a
975 /// warning in the future, possibly with [type ascription] providing a
976 /// convenient way to work around the current issues. See [RFC 401] for
977 /// historical context.
979 /// [type ascription]: https://github.com/rust-lang/rust/issues/23416
980 /// [RFC 401]: https://github.com/rust-lang/rfcs/blob/master/text/0401-coercions.md
981 pub TRIVIAL_NUMERIC_CASTS,
983 "detects trivial casts of numeric types which could be removed"
987 /// The `private_in_public` lint detects private items in public
988 /// interfaces not caught by the old implementation.
993 /// # #![allow(unused)]
998 /// impl super::SemiPriv {
999 /// pub fn f(_: Priv) {}
1009 /// The visibility rules are intended to prevent exposing private items in
1010 /// public interfaces. This is a [future-incompatible] lint to transition
1011 /// this to a hard error in the future. See [issue #34537] for more
1014 /// [issue #34537]: https://github.com/rust-lang/rust/issues/34537
1015 /// [future-incompatible]: ../index.md#future-incompatible-lints
1016 pub PRIVATE_IN_PUBLIC,
1018 "detect private items in public interfaces not caught by the old implementation",
1019 @future_incompatible = FutureIncompatibleInfo {
1020 reference: "issue #34537 <https://github.com/rust-lang/rust/issues/34537>",
1025 /// The `exported_private_dependencies` lint detects private dependencies
1026 /// that are exposed in a public interface.
1030 /// ```rust,ignore (needs-dependency)
1031 /// pub fn foo() -> Option<some_private_dependency::Thing> {
1036 /// This will produce:
1039 /// warning: type `bar::Thing` from private dependency 'bar' in public interface
1040 /// --> src/lib.rs:3:1
1042 /// 3 | pub fn foo() -> Option<bar::Thing> {
1043 /// | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1045 /// = note: `#[warn(exported_private_dependencies)]` on by default
1050 /// Dependencies can be marked as "private" to indicate that they are not
1051 /// exposed in the public interface of a crate. This can be used by Cargo
1052 /// to independently resolve those dependencies because it can assume it
1053 /// does not need to unify them with other packages using that same
1054 /// dependency. This lint is an indication of a violation of that
1057 /// To fix this, avoid exposing the dependency in your public interface.
1058 /// Or, switch the dependency to a public dependency.
1060 /// Note that support for this is only available on the nightly channel.
1061 /// See [RFC 1977] for more details, as well as the [Cargo documentation].
1063 /// [RFC 1977]: https://github.com/rust-lang/rfcs/blob/master/text/1977-public-private-dependencies.md
1064 /// [Cargo documentation]: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#public-dependency
1065 pub EXPORTED_PRIVATE_DEPENDENCIES,
1067 "public interface leaks type from a private dependency"
1071 /// The `pub_use_of_private_extern_crate` lint detects a specific
1072 /// situation of re-exporting a private `extern crate`.
1076 /// ```rust,compile_fail
1077 /// extern crate core;
1078 /// pub use core as reexported_core;
1085 /// A public `use` declaration should not be used to publicly re-export a
1086 /// private `extern crate`. `pub extern crate` should be used instead.
1088 /// This was historically allowed, but is not the intended behavior
1089 /// according to the visibility rules. This is a [future-incompatible]
1090 /// lint to transition this to a hard error in the future. See [issue
1091 /// #34537] for more details.
1093 /// [issue #34537]: https://github.com/rust-lang/rust/issues/34537
1094 /// [future-incompatible]: ../index.md#future-incompatible-lints
1095 pub PUB_USE_OF_PRIVATE_EXTERN_CRATE,
1097 "detect public re-exports of private extern crates",
1098 @future_incompatible = FutureIncompatibleInfo {
1099 reference: "issue #34537 <https://github.com/rust-lang/rust/issues/34537>",
1104 /// The `invalid_type_param_default` lint detects type parameter defaults
1105 /// erroneously allowed in an invalid location.
1109 /// ```rust,compile_fail
1110 /// fn foo<T=i32>(t: T) {}
1117 /// Default type parameters were only intended to be allowed in certain
1118 /// situations, but historically the compiler allowed them everywhere.
1119 /// This is a [future-incompatible] lint to transition this to a hard
1120 /// error in the future. See [issue #36887] for more details.
1122 /// [issue #36887]: https://github.com/rust-lang/rust/issues/36887
1123 /// [future-incompatible]: ../index.md#future-incompatible-lints
1124 pub INVALID_TYPE_PARAM_DEFAULT,
1126 "type parameter default erroneously allowed in invalid location",
1127 @future_incompatible = FutureIncompatibleInfo {
1128 reference: "issue #36887 <https://github.com/rust-lang/rust/issues/36887>",
1133 /// The `renamed_and_removed_lints` lint detects lints that have been
1134 /// renamed or removed.
1139 /// #![deny(raw_pointer_derive)]
1146 /// To fix this, either remove the lint or use the new name. This can help
1147 /// avoid confusion about lints that are no longer valid, and help
1148 /// maintain consistency for renamed lints.
1149 pub RENAMED_AND_REMOVED_LINTS,
1151 "lints that have been renamed or removed"
1155 /// The `unaligned_references` lint detects unaligned references to fields
1156 /// of [packed] structs.
1158 /// [packed]: https://doc.rust-lang.org/reference/type-layout.html#the-alignment-modifiers
1164 /// pub struct Foo {
1171 /// let foo = Foo { field1: 0, field2: 0 };
1172 /// let _ = &foo.field1;
1173 /// println!("{}", foo.field1); // An implicit `&` is added here, triggering the lint.
1182 /// Creating a reference to an insufficiently aligned packed field is [undefined behavior] and
1183 /// should be disallowed. Using an `unsafe` block does not change anything about this. Instead,
1184 /// the code should do a copy of the data in the packed field or use raw pointers and unaligned
1185 /// accesses. See [issue #82523] for more information.
1187 /// [undefined behavior]: https://doc.rust-lang.org/reference/behavior-considered-undefined.html
1188 /// [issue #82523]: https://github.com/rust-lang/rust/issues/82523
1189 pub UNALIGNED_REFERENCES,
1191 "detects unaligned references to fields of packed structs",
1192 @future_incompatible = FutureIncompatibleInfo {
1193 reference: "issue #82523 <https://github.com/rust-lang/rust/issues/82523>",
1194 reason: FutureIncompatibilityReason::FutureReleaseErrorReportNow,
1196 report_in_external_macro
1200 /// The `const_item_mutation` lint detects attempts to mutate a `const`
1206 /// const FOO: [i32; 1] = [0];
1210 /// // This will print "[0]".
1211 /// println!("{:?}", FOO);
1219 /// Trying to directly mutate a `const` item is almost always a mistake.
1220 /// What is happening in the example above is that a temporary copy of the
1221 /// `const` is mutated, but the original `const` is not. Each time you
1222 /// refer to the `const` by name (such as `FOO` in the example above), a
1223 /// separate copy of the value is inlined at that location.
1225 /// This lint checks for writing directly to a field (`FOO.field =
1226 /// some_value`) or array entry (`FOO[0] = val`), or taking a mutable
1227 /// reference to the const item (`&mut FOO`), including through an
1228 /// autoderef (`FOO.some_mut_self_method()`).
1230 /// There are various alternatives depending on what you are trying to
1233 /// * First, always reconsider using mutable globals, as they can be
1234 /// difficult to use correctly, and can make the code more difficult to
1235 /// use or understand.
1236 /// * If you are trying to perform a one-time initialization of a global:
1237 /// * If the value can be computed at compile-time, consider using
1238 /// const-compatible values (see [Constant Evaluation]).
1239 /// * For more complex single-initialization cases, consider using a
1240 /// third-party crate, such as [`lazy_static`] or [`once_cell`].
1241 /// * If you are using the [nightly channel], consider the new
1242 /// [`lazy`] module in the standard library.
1243 /// * If you truly need a mutable global, consider using a [`static`],
1244 /// which has a variety of options:
1245 /// * Simple data types can be directly defined and mutated with an
1246 /// [`atomic`] type.
1247 /// * More complex types can be placed in a synchronization primitive
1248 /// like a [`Mutex`], which can be initialized with one of the options
1250 /// * A [mutable `static`] is a low-level primitive, requiring unsafe.
1251 /// Typically This should be avoided in preference of something
1252 /// higher-level like one of the above.
1254 /// [Constant Evaluation]: https://doc.rust-lang.org/reference/const_eval.html
1255 /// [`static`]: https://doc.rust-lang.org/reference/items/static-items.html
1256 /// [mutable `static`]: https://doc.rust-lang.org/reference/items/static-items.html#mutable-statics
1257 /// [`lazy`]: https://doc.rust-lang.org/nightly/std/lazy/index.html
1258 /// [`lazy_static`]: https://crates.io/crates/lazy_static
1259 /// [`once_cell`]: https://crates.io/crates/once_cell
1260 /// [`atomic`]: https://doc.rust-lang.org/std/sync/atomic/index.html
1261 /// [`Mutex`]: https://doc.rust-lang.org/std/sync/struct.Mutex.html
1262 pub CONST_ITEM_MUTATION,
1264 "detects attempts to mutate a `const` item",
1268 /// The `patterns_in_fns_without_body` lint detects `mut` identifier
1269 /// patterns as a parameter in functions without a body.
1273 /// ```rust,compile_fail
1275 /// fn foo(mut arg: u8);
1283 /// To fix this, remove `mut` from the parameter in the trait definition;
1284 /// it can be used in the implementation. That is, the following is OK:
1288 /// fn foo(arg: u8); // Removed `mut` here
1291 /// impl Trait for i32 {
1292 /// fn foo(mut arg: u8) { // `mut` here is OK
1298 /// Trait definitions can define functions without a body to specify a
1299 /// function that implementors must define. The parameter names in the
1300 /// body-less functions are only allowed to be `_` or an [identifier] for
1301 /// documentation purposes (only the type is relevant). Previous versions
1302 /// of the compiler erroneously allowed [identifier patterns] with the
1303 /// `mut` keyword, but this was not intended to be allowed. This is a
1304 /// [future-incompatible] lint to transition this to a hard error in the
1305 /// future. See [issue #35203] for more details.
1307 /// [identifier]: https://doc.rust-lang.org/reference/identifiers.html
1308 /// [identifier patterns]: https://doc.rust-lang.org/reference/patterns.html#identifier-patterns
1309 /// [issue #35203]: https://github.com/rust-lang/rust/issues/35203
1310 /// [future-incompatible]: ../index.md#future-incompatible-lints
1311 pub PATTERNS_IN_FNS_WITHOUT_BODY,
1313 "patterns in functions without body were erroneously allowed",
1314 @future_incompatible = FutureIncompatibleInfo {
1315 reference: "issue #35203 <https://github.com/rust-lang/rust/issues/35203>",
1320 /// The `missing_fragment_specifier` lint is issued when an unused pattern in a
1321 /// `macro_rules!` macro definition has a meta-variable (e.g. `$e`) that is not
1322 /// followed by a fragment specifier (e.g. `:expr`).
1324 /// This warning can always be fixed by removing the unused pattern in the
1325 /// `macro_rules!` macro definition.
1329 /// ```rust,compile_fail
1330 /// macro_rules! foo {
1344 /// To fix this, remove the unused pattern from the `macro_rules!` macro definition:
1347 /// macro_rules! foo {
1354 pub MISSING_FRAGMENT_SPECIFIER,
1356 "detects missing fragment specifiers in unused `macro_rules!` patterns",
1357 @future_incompatible = FutureIncompatibleInfo {
1358 reference: "issue #40107 <https://github.com/rust-lang/rust/issues/40107>",
1363 /// The `late_bound_lifetime_arguments` lint detects generic lifetime
1364 /// arguments in path segments with late bound lifetime parameters.
1372 /// fn late<'a, 'b>(self, _: &'a u8, _: &'b u8) {}
1376 /// S.late::<'static>(&0, &0);
1384 /// It is not clear how to provide arguments for early-bound lifetime
1385 /// parameters if they are intermixed with late-bound parameters in the
1386 /// same list. For now, providing any explicit arguments will trigger this
1387 /// lint if late-bound parameters are present, so in the future a solution
1388 /// can be adopted without hitting backward compatibility issues. This is
1389 /// a [future-incompatible] lint to transition this to a hard error in the
1390 /// future. See [issue #42868] for more details, along with a description
1391 /// of the difference between early and late-bound parameters.
1393 /// [issue #42868]: https://github.com/rust-lang/rust/issues/42868
1394 /// [future-incompatible]: ../index.md#future-incompatible-lints
1395 pub LATE_BOUND_LIFETIME_ARGUMENTS,
1397 "detects generic lifetime arguments in path segments with late bound lifetime parameters",
1398 @future_incompatible = FutureIncompatibleInfo {
1399 reference: "issue #42868 <https://github.com/rust-lang/rust/issues/42868>",
1404 /// The `order_dependent_trait_objects` lint detects a trait coherency
1405 /// violation that would allow creating two trait impls for the same
1406 /// dynamic trait object involving marker traits.
1410 /// ```rust,compile_fail
1411 /// pub trait Trait {}
1413 /// impl Trait for dyn Send + Sync { }
1414 /// impl Trait for dyn Sync + Send { }
1421 /// A previous bug caused the compiler to interpret traits with different
1422 /// orders (such as `Send + Sync` and `Sync + Send`) as distinct types
1423 /// when they were intended to be treated the same. This allowed code to
1424 /// define separate trait implementations when there should be a coherence
1425 /// error. This is a [future-incompatible] lint to transition this to a
1426 /// hard error in the future. See [issue #56484] for more details.
1428 /// [issue #56484]: https://github.com/rust-lang/rust/issues/56484
1429 /// [future-incompatible]: ../index.md#future-incompatible-lints
1430 pub ORDER_DEPENDENT_TRAIT_OBJECTS,
1432 "trait-object types were treated as different depending on marker-trait order",
1433 @future_incompatible = FutureIncompatibleInfo {
1434 reference: "issue #56484 <https://github.com/rust-lang/rust/issues/56484>",
1439 /// The `coherence_leak_check` lint detects conflicting implementations of
1440 /// a trait that are only distinguished by the old leak-check code.
1445 /// trait SomeTrait { }
1446 /// impl SomeTrait for for<'a> fn(&'a u8) { }
1447 /// impl<'a> SomeTrait for fn(&'a u8) { }
1454 /// In the past, the compiler would accept trait implementations for
1455 /// identical functions that differed only in where the lifetime binder
1456 /// appeared. Due to a change in the borrow checker implementation to fix
1457 /// several bugs, this is no longer allowed. However, since this affects
1458 /// existing code, this is a [future-incompatible] lint to transition this
1459 /// to a hard error in the future.
1461 /// Code relying on this pattern should introduce "[newtypes]",
1462 /// like `struct Foo(for<'a> fn(&'a u8))`.
1464 /// See [issue #56105] for more details.
1466 /// [issue #56105]: https://github.com/rust-lang/rust/issues/56105
1467 /// [newtypes]: https://doc.rust-lang.org/book/ch19-04-advanced-types.html#using-the-newtype-pattern-for-type-safety-and-abstraction
1468 /// [future-incompatible]: ../index.md#future-incompatible-lints
1469 pub COHERENCE_LEAK_CHECK,
1471 "distinct impls distinguished only by the leak-check code",
1472 @future_incompatible = FutureIncompatibleInfo {
1473 reference: "issue #56105 <https://github.com/rust-lang/rust/issues/56105>",
1478 /// The `deprecated` lint detects use of deprecated items.
1495 /// Items may be marked "deprecated" with the [`deprecated` attribute] to
1496 /// indicate that they should no longer be used. Usually the attribute
1497 /// should include a note on what to use instead, or check the
1500 /// [`deprecated` attribute]: https://doc.rust-lang.org/reference/attributes/diagnostics.html#the-deprecated-attribute
1503 "detects use of deprecated items",
1504 report_in_external_macro
1508 /// The `unused_unsafe` lint detects unnecessary use of an `unsafe` block.
1520 /// If nothing within the block requires `unsafe`, then remove the
1521 /// `unsafe` marker because it is not required and may cause confusion.
1524 "unnecessary use of an `unsafe` block"
1528 /// The `unused_mut` lint detects mut variables which don't need to be
1541 /// The preferred style is to only mark variables as `mut` if it is
1545 "detect mut variables which don't need to be mutable"
1549 /// The `unconditional_recursion` lint detects functions that cannot
1550 /// return without calling themselves.
1564 /// It is usually a mistake to have a recursive call that does not have
1565 /// some condition to cause it to terminate. If you really intend to have
1566 /// an infinite loop, using a `loop` expression is recommended.
1567 pub UNCONDITIONAL_RECURSION,
1569 "functions that cannot return without calling themselves"
1573 /// The `single_use_lifetimes` lint detects lifetimes that are only used
1578 /// ```rust,compile_fail
1579 /// #![deny(single_use_lifetimes)]
1581 /// fn foo<'a>(x: &'a u32) {}
1588 /// Specifying an explicit lifetime like `'a` in a function or `impl`
1589 /// should only be used to link together two things. Otherwise, you should
1590 /// just use `'_` to indicate that the lifetime is not linked to anything,
1591 /// or elide the lifetime altogether if possible.
1593 /// This lint is "allow" by default because it was introduced at a time
1594 /// when `'_` and elided lifetimes were first being introduced, and this
1595 /// lint would be too noisy. Also, there are some known false positives
1596 /// that it produces. See [RFC 2115] for historical context, and [issue
1597 /// #44752] for more details.
1599 /// [RFC 2115]: https://github.com/rust-lang/rfcs/blob/master/text/2115-argument-lifetimes.md
1600 /// [issue #44752]: https://github.com/rust-lang/rust/issues/44752
1601 pub SINGLE_USE_LIFETIMES,
1603 "detects lifetime parameters that are only used once"
1607 /// The `unused_lifetimes` lint detects lifetime parameters that are never
1612 /// ```rust,compile_fail
1613 /// #[deny(unused_lifetimes)]
1615 /// pub fn foo<'a>() {}
1622 /// Unused lifetime parameters may signal a mistake or unfinished code.
1623 /// Consider removing the parameter.
1624 pub UNUSED_LIFETIMES,
1626 "detects lifetime parameters that are never used"
1630 /// The `tyvar_behind_raw_pointer` lint detects raw pointer to an
1631 /// inference variable.
1635 /// ```rust,edition2015
1637 /// let data = std::ptr::null();
1638 /// let _ = &data as *const *const ();
1640 /// if data.is_null() {}
1647 /// This kind of inference was previously allowed, but with the future
1648 /// arrival of [arbitrary self types], this can introduce ambiguity. To
1649 /// resolve this, use an explicit type instead of relying on type
1652 /// This is a [future-incompatible] lint to transition this to a hard
1653 /// error in the 2018 edition. See [issue #46906] for more details. This
1654 /// is currently a hard-error on the 2018 edition, and is "warn" by
1655 /// default in the 2015 edition.
1657 /// [arbitrary self types]: https://github.com/rust-lang/rust/issues/44874
1658 /// [issue #46906]: https://github.com/rust-lang/rust/issues/46906
1659 /// [future-incompatible]: ../index.md#future-incompatible-lints
1660 pub TYVAR_BEHIND_RAW_POINTER,
1662 "raw pointer to an inference variable",
1663 @future_incompatible = FutureIncompatibleInfo {
1664 reference: "issue #46906 <https://github.com/rust-lang/rust/issues/46906>",
1665 reason: FutureIncompatibilityReason::EditionError(Edition::Edition2018),
1670 /// The `elided_lifetimes_in_paths` lint detects the use of hidden
1671 /// lifetime parameters.
1675 /// ```rust,compile_fail
1676 /// #![deny(elided_lifetimes_in_paths)]
1677 /// struct Foo<'a> {
1681 /// fn foo(x: &Foo) {
1689 /// Elided lifetime parameters can make it difficult to see at a glance
1690 /// that borrowing is occurring. This lint ensures that lifetime
1691 /// parameters are always explicitly stated, even if it is the `'_`
1692 /// [placeholder lifetime].
1694 /// This lint is "allow" by default because it has some known issues, and
1695 /// may require a significant transition for old code.
1697 /// [placeholder lifetime]: https://doc.rust-lang.org/reference/lifetime-elision.html#lifetime-elision-in-functions
1698 pub ELIDED_LIFETIMES_IN_PATHS,
1700 "hidden lifetime parameters in types are deprecated",
1705 /// The `bare_trait_objects` lint suggests using `dyn Trait` for trait
1710 /// ```rust,edition2018
1713 /// fn takes_trait_object(_: Box<Trait>) {
1721 /// Without the `dyn` indicator, it can be ambiguous or confusing when
1722 /// reading code as to whether or not you are looking at a trait object.
1723 /// The `dyn` keyword makes it explicit, and adds a symmetry to contrast
1724 /// with [`impl Trait`].
1726 /// [`impl Trait`]: https://doc.rust-lang.org/book/ch10-02-traits.html#traits-as-parameters
1727 pub BARE_TRAIT_OBJECTS,
1729 "suggest using `dyn Trait` for trait objects",
1730 @future_incompatible = FutureIncompatibleInfo {
1731 reference: "<https://doc.rust-lang.org/nightly/edition-guide/rust-2021/warnings-promoted-to-error.html>",
1732 reason: FutureIncompatibilityReason::EditionError(Edition::Edition2021),
1737 /// The `absolute_paths_not_starting_with_crate` lint detects fully
1738 /// qualified paths that start with a module name instead of `crate`,
1739 /// `self`, or an extern crate name
1743 /// ```rust,edition2015,compile_fail
1744 /// #![deny(absolute_paths_not_starting_with_crate)]
1759 /// Rust [editions] allow the language to evolve without breaking
1760 /// backwards compatibility. This lint catches code that uses absolute
1761 /// paths in the style of the 2015 edition. In the 2015 edition, absolute
1762 /// paths (those starting with `::`) refer to either the crate root or an
1763 /// external crate. In the 2018 edition it was changed so that they only
1764 /// refer to external crates. The path prefix `crate::` should be used
1765 /// instead to reference items from the crate root.
1767 /// If you switch the compiler from the 2015 to 2018 edition without
1768 /// updating the code, then it will fail to compile if the old style paths
1769 /// are used. You can manually change the paths to use the `crate::`
1770 /// prefix to transition to the 2018 edition.
1772 /// This lint solves the problem automatically. It is "allow" by default
1773 /// because the code is perfectly valid in the 2015 edition. The [`cargo
1774 /// fix`] tool with the `--edition` flag will switch this lint to "warn"
1775 /// and automatically apply the suggested fix from the compiler. This
1776 /// provides a completely automated way to update old code to the 2018
1779 /// [editions]: https://doc.rust-lang.org/edition-guide/
1780 /// [`cargo fix`]: https://doc.rust-lang.org/cargo/commands/cargo-fix.html
1781 pub ABSOLUTE_PATHS_NOT_STARTING_WITH_CRATE,
1783 "fully qualified paths that start with a module name \
1784 instead of `crate`, `self`, or an extern crate name",
1785 @future_incompatible = FutureIncompatibleInfo {
1786 reference: "issue #53130 <https://github.com/rust-lang/rust/issues/53130>",
1787 reason: FutureIncompatibilityReason::EditionError(Edition::Edition2018),
1792 /// The `illegal_floating_point_literal_pattern` lint detects
1793 /// floating-point literals used in patterns.
1810 /// Previous versions of the compiler accepted floating-point literals in
1811 /// patterns, but it was later determined this was a mistake. The
1812 /// semantics of comparing floating-point values may not be clear in a
1813 /// pattern when contrasted with "structural equality". Typically you can
1814 /// work around this by using a [match guard], such as:
1820 /// y if y == 5.0 => {}
1825 /// This is a [future-incompatible] lint to transition this to a hard
1826 /// error in the future. See [issue #41620] for more details.
1828 /// [issue #41620]: https://github.com/rust-lang/rust/issues/41620
1829 /// [match guard]: https://doc.rust-lang.org/reference/expressions/match-expr.html#match-guards
1830 /// [future-incompatible]: ../index.md#future-incompatible-lints
1831 pub ILLEGAL_FLOATING_POINT_LITERAL_PATTERN,
1833 "floating-point literals cannot be used in patterns",
1834 @future_incompatible = FutureIncompatibleInfo {
1835 reference: "issue #41620 <https://github.com/rust-lang/rust/issues/41620>",
1840 /// The `unstable_name_collisions` lint detects that you have used a name
1841 /// that the standard library plans to add in the future.
1846 /// trait MyIterator : Iterator {
1847 /// // is_sorted is an unstable method that already exists on the Iterator trait
1848 /// fn is_sorted(self) -> bool where Self: Sized {true}
1851 /// impl<T: ?Sized> MyIterator for T where T: Iterator { }
1853 /// let x = vec![1, 2, 3];
1854 /// let _ = x.iter().is_sorted();
1861 /// When new methods are added to traits in the standard library, they are
1862 /// usually added in an "unstable" form which is only available on the
1863 /// [nightly channel] with a [`feature` attribute]. If there is any
1864 /// pre-existing code which extends a trait to have a method with the same
1865 /// name, then the names will collide. In the future, when the method is
1866 /// stabilized, this will cause an error due to the ambiguity. This lint
1867 /// is an early-warning to let you know that there may be a collision in
1868 /// the future. This can be avoided by adding type annotations to
1869 /// disambiguate which trait method you intend to call, such as
1870 /// `MyIterator::is_sorted(my_iter)` or renaming or removing the method.
1872 /// [nightly channel]: https://doc.rust-lang.org/book/appendix-07-nightly-rust.html
1873 /// [`feature` attribute]: https://doc.rust-lang.org/nightly/unstable-book/
1874 pub UNSTABLE_NAME_COLLISIONS,
1876 "detects name collision with an existing but unstable method",
1877 @future_incompatible = FutureIncompatibleInfo {
1878 reason: FutureIncompatibilityReason::Custom(
1879 "once this associated item is added to the standard library, \
1880 the ambiguity may cause an error or change in behavior!"
1882 reference: "issue #48919 <https://github.com/rust-lang/rust/issues/48919>",
1883 // Note: this item represents future incompatibility of all unstable functions in the
1884 // standard library, and thus should never be removed or changed to an error.
1889 /// The `irrefutable_let_patterns` lint detects [irrefutable patterns]
1890 /// in [`if let`]s, [`while let`]s, and `if let` guards.
1895 /// if let _ = 123 {
1896 /// println!("always runs!");
1904 /// There usually isn't a reason to have an irrefutable pattern in an
1905 /// `if let` or `while let` statement, because the pattern will always match
1906 /// successfully. A [`let`] or [`loop`] statement will suffice. However,
1907 /// when generating code with a macro, forbidding irrefutable patterns
1908 /// would require awkward workarounds in situations where the macro
1909 /// doesn't know if the pattern is refutable or not. This lint allows
1910 /// macros to accept this form, while alerting for a possibly incorrect
1911 /// use in normal code.
1913 /// See [RFC 2086] for more details.
1915 /// [irrefutable patterns]: https://doc.rust-lang.org/reference/patterns.html#refutability
1916 /// [`if let`]: https://doc.rust-lang.org/reference/expressions/if-expr.html#if-let-expressions
1917 /// [`while let`]: https://doc.rust-lang.org/reference/expressions/loop-expr.html#predicate-pattern-loops
1918 /// [`let`]: https://doc.rust-lang.org/reference/statements.html#let-statements
1919 /// [`loop`]: https://doc.rust-lang.org/reference/expressions/loop-expr.html#infinite-loops
1920 /// [RFC 2086]: https://github.com/rust-lang/rfcs/blob/master/text/2086-allow-if-let-irrefutables.md
1921 pub IRREFUTABLE_LET_PATTERNS,
1923 "detects irrefutable patterns in `if let` and `while let` statements"
1927 /// The `unused_labels` lint detects [labels] that are never used.
1929 /// [labels]: https://doc.rust-lang.org/reference/expressions/loop-expr.html#loop-labels
1934 /// 'unused_label: loop {}
1941 /// Unused labels may signal a mistake or unfinished code. To silence the
1942 /// warning for the individual label, prefix it with an underscore such as
1946 "detects labels that are never used"
1950 /// The `where_clauses_object_safety` lint detects for [object safety] of
1951 /// [where clauses].
1953 /// [object safety]: https://doc.rust-lang.org/reference/items/traits.html#object-safety
1954 /// [where clauses]: https://doc.rust-lang.org/reference/items/generics.html#where-clauses
1961 /// trait X { fn foo(&self) where Self: Trait; }
1963 /// impl X for () { fn foo(&self) {} }
1965 /// impl Trait for dyn X {}
1967 /// // Segfault at opt-level 0, SIGILL otherwise.
1968 /// pub fn main() { <dyn X as X>::foo(&()); }
1975 /// The compiler previously allowed these object-unsafe bounds, which was
1976 /// incorrect. This is a [future-incompatible] lint to transition this to
1977 /// a hard error in the future. See [issue #51443] for more details.
1979 /// [issue #51443]: https://github.com/rust-lang/rust/issues/51443
1980 /// [future-incompatible]: ../index.md#future-incompatible-lints
1981 pub WHERE_CLAUSES_OBJECT_SAFETY,
1983 "checks the object safety of where clauses",
1984 @future_incompatible = FutureIncompatibleInfo {
1985 reference: "issue #51443 <https://github.com/rust-lang/rust/issues/51443>",
1990 /// The `proc_macro_derive_resolution_fallback` lint detects proc macro
1991 /// derives using inaccessible names from parent modules.
1995 /// ```rust,ignore (proc-macro)
1997 /// #![crate_type = "proc-macro"]
1999 /// extern crate proc_macro;
2001 /// use proc_macro::*;
2003 /// #[proc_macro_derive(Foo)]
2004 /// pub fn foo1(a: TokenStream) -> TokenStream {
2006 /// "mod __bar { static mut BAR: Option<Something> = None; }".parse().unwrap()
2010 /// ```rust,ignore (needs-dependency)
2013 /// extern crate foo;
2015 /// struct Something;
2023 /// This will produce:
2026 /// warning: cannot find type `Something` in this scope
2027 /// --> src/main.rs:8:10
2029 /// 8 | #[derive(Foo)]
2030 /// | ^^^ names from parent modules are not accessible without an explicit import
2032 /// = note: `#[warn(proc_macro_derive_resolution_fallback)]` on by default
2033 /// = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
2034 /// = note: for more information, see issue #50504 <https://github.com/rust-lang/rust/issues/50504>
2039 /// If a proc-macro generates a module, the compiler unintentionally
2040 /// allowed items in that module to refer to items in the crate root
2041 /// without importing them. This is a [future-incompatible] lint to
2042 /// transition this to a hard error in the future. See [issue #50504] for
2045 /// [issue #50504]: https://github.com/rust-lang/rust/issues/50504
2046 /// [future-incompatible]: ../index.md#future-incompatible-lints
2047 pub PROC_MACRO_DERIVE_RESOLUTION_FALLBACK,
2049 "detects proc macro derives using inaccessible names from parent modules",
2050 @future_incompatible = FutureIncompatibleInfo {
2051 reference: "issue #83583 <https://github.com/rust-lang/rust/issues/83583>",
2052 reason: FutureIncompatibilityReason::FutureReleaseErrorReportNow,
2057 /// The `macro_use_extern_crate` lint detects the use of the
2058 /// [`macro_use` attribute].
2062 /// ```rust,ignore (needs extern crate)
2063 /// #![deny(macro_use_extern_crate)]
2066 /// extern crate serde_json;
2069 /// let _ = json!{{}};
2073 /// This will produce:
2076 /// error: deprecated `#[macro_use]` attribute used to import macros should be replaced at use sites with a `use` item to import the macro instead
2077 /// --> src/main.rs:3:1
2079 /// 3 | #[macro_use]
2082 /// note: the lint level is defined here
2083 /// --> src/main.rs:1:9
2085 /// 1 | #![deny(macro_use_extern_crate)]
2086 /// | ^^^^^^^^^^^^^^^^^^^^^^
2091 /// The [`macro_use` attribute] on an [`extern crate`] item causes
2092 /// macros in that external crate to be brought into the prelude of the
2093 /// crate, making the macros in scope everywhere. As part of the efforts
2094 /// to simplify handling of dependencies in the [2018 edition], the use of
2095 /// `extern crate` is being phased out. To bring macros from extern crates
2096 /// into scope, it is recommended to use a [`use` import].
2098 /// This lint is "allow" by default because this is a stylistic choice
2099 /// that has not been settled, see [issue #52043] for more information.
2101 /// [`macro_use` attribute]: https://doc.rust-lang.org/reference/macros-by-example.html#the-macro_use-attribute
2102 /// [`use` import]: https://doc.rust-lang.org/reference/items/use-declarations.html
2103 /// [issue #52043]: https://github.com/rust-lang/rust/issues/52043
2104 pub MACRO_USE_EXTERN_CRATE,
2106 "the `#[macro_use]` attribute is now deprecated in favor of using macros \
2107 via the module system"
2111 /// The `macro_expanded_macro_exports_accessed_by_absolute_paths` lint
2112 /// detects macro-expanded [`macro_export`] macros from the current crate
2113 /// that cannot be referred to by absolute paths.
2115 /// [`macro_export`]: https://doc.rust-lang.org/reference/macros-by-example.html#path-based-scope
2119 /// ```rust,compile_fail
2120 /// macro_rules! define_exported {
2123 /// macro_rules! exported {
2129 /// define_exported!();
2132 /// crate::exported!();
2140 /// The intent is that all macros marked with the `#[macro_export]`
2141 /// attribute are made available in the root of the crate. However, when a
2142 /// `macro_rules!` definition is generated by another macro, the macro
2143 /// expansion is unable to uphold this rule. This is a
2144 /// [future-incompatible] lint to transition this to a hard error in the
2145 /// future. See [issue #53495] for more details.
2147 /// [issue #53495]: https://github.com/rust-lang/rust/issues/53495
2148 /// [future-incompatible]: ../index.md#future-incompatible-lints
2149 pub MACRO_EXPANDED_MACRO_EXPORTS_ACCESSED_BY_ABSOLUTE_PATHS,
2151 "macro-expanded `macro_export` macros from the current crate \
2152 cannot be referred to by absolute paths",
2153 @future_incompatible = FutureIncompatibleInfo {
2154 reference: "issue #52234 <https://github.com/rust-lang/rust/issues/52234>",
2160 /// The `explicit_outlives_requirements` lint detects unnecessary
2161 /// lifetime bounds that can be inferred.
2165 /// ```rust,compile_fail
2166 /// # #![allow(unused)]
2167 /// #![deny(explicit_outlives_requirements)]
2169 /// struct SharedRef<'a, T>
2181 /// If a `struct` contains a reference, such as `&'a T`, the compiler
2182 /// requires that `T` outlives the lifetime `'a`. This historically
2183 /// required writing an explicit lifetime bound to indicate this
2184 /// requirement. However, this can be overly explicit, causing clutter and
2185 /// unnecessary complexity. The language was changed to automatically
2186 /// infer the bound if it is not specified. Specifically, if the struct
2187 /// contains a reference, directly or indirectly, to `T` with lifetime
2188 /// `'x`, then it will infer that `T: 'x` is a requirement.
2190 /// This lint is "allow" by default because it can be noisy for existing
2191 /// code that already had these requirements. This is a stylistic choice,
2192 /// as it is still valid to explicitly state the bound. It also has some
2193 /// false positives that can cause confusion.
2195 /// See [RFC 2093] for more details.
2197 /// [RFC 2093]: https://github.com/rust-lang/rfcs/blob/master/text/2093-infer-outlives.md
2198 pub EXPLICIT_OUTLIVES_REQUIREMENTS,
2200 "outlives requirements can be inferred"
2204 /// The `indirect_structural_match` lint detects a `const` in a pattern
2205 /// that manually implements [`PartialEq`] and [`Eq`].
2207 /// [`PartialEq`]: https://doc.rust-lang.org/std/cmp/trait.PartialEq.html
2208 /// [`Eq`]: https://doc.rust-lang.org/std/cmp/trait.Eq.html
2212 /// ```rust,compile_fail
2213 /// #![deny(indirect_structural_match)]
2215 /// struct NoDerive(i32);
2216 /// impl PartialEq for NoDerive { fn eq(&self, _: &Self) -> bool { false } }
2217 /// impl Eq for NoDerive { }
2218 /// #[derive(PartialEq, Eq)]
2219 /// struct WrapParam<T>(T);
2220 /// const WRAP_INDIRECT_PARAM: & &WrapParam<NoDerive> = & &WrapParam(NoDerive(0));
2222 /// match WRAP_INDIRECT_PARAM {
2223 /// WRAP_INDIRECT_PARAM => { }
2233 /// The compiler unintentionally accepted this form in the past. This is a
2234 /// [future-incompatible] lint to transition this to a hard error in the
2235 /// future. See [issue #62411] for a complete description of the problem,
2236 /// and some possible solutions.
2238 /// [issue #62411]: https://github.com/rust-lang/rust/issues/62411
2239 /// [future-incompatible]: ../index.md#future-incompatible-lints
2240 pub INDIRECT_STRUCTURAL_MATCH,
2242 "constant used in pattern contains value of non-structural-match type in a field or a variant",
2243 @future_incompatible = FutureIncompatibleInfo {
2244 reference: "issue #62411 <https://github.com/rust-lang/rust/issues/62411>",
2249 /// The `deprecated_in_future` lint is internal to rustc and should not be
2250 /// used by user code.
2252 /// This lint is only enabled in the standard library. It works with the
2253 /// use of `#[deprecated]` with a `since` field of a version in the future.
2254 /// This allows something to be marked as deprecated in a future version,
2255 /// and then this lint will ensure that the item is no longer used in the
2256 /// standard library. See the [stability documentation] for more details.
2258 /// [stability documentation]: https://rustc-dev-guide.rust-lang.org/stability.html#deprecated
2259 pub DEPRECATED_IN_FUTURE,
2261 "detects use of items that will be deprecated in a future version",
2262 report_in_external_macro
2266 /// The `pointer_structural_match` lint detects pointers used in patterns whose behaviour
2267 /// cannot be relied upon across compiler versions and optimization levels.
2271 /// ```rust,compile_fail
2272 /// #![deny(pointer_structural_match)]
2273 /// fn foo(a: usize, b: usize) -> usize { a + b }
2274 /// const FOO: fn(usize, usize) -> usize = foo;
2287 /// Previous versions of Rust allowed function pointers and wide raw pointers in patterns.
2288 /// While these work in many cases as expected by users, it is possible that due to
2289 /// optimizations pointers are "not equal to themselves" or pointers to different functions
2290 /// compare as equal during runtime. This is because LLVM optimizations can deduplicate
2291 /// functions if their bodies are the same, thus also making pointers to these functions point
2292 /// to the same location. Additionally functions may get duplicated if they are instantiated
2293 /// in different crates and not deduplicated again via LTO.
2294 pub POINTER_STRUCTURAL_MATCH,
2296 "pointers are not structural-match",
2297 @future_incompatible = FutureIncompatibleInfo {
2298 reference: "issue #62411 <https://github.com/rust-lang/rust/issues/70861>",
2303 /// The `nontrivial_structural_match` lint detects constants that are used in patterns,
2304 /// whose type is not structural-match and whose initializer body actually uses values
2305 /// that are not structural-match. So `Option<NotStructuralMatch>` is ok if the constant
2310 /// ```rust,compile_fail
2311 /// #![deny(nontrivial_structural_match)]
2313 /// #[derive(Copy, Clone, Debug)]
2314 /// struct NoDerive(u32);
2315 /// impl PartialEq for NoDerive { fn eq(&self, _: &Self) -> bool { false } }
2316 /// impl Eq for NoDerive { }
2318 /// const INDEX: Option<NoDerive> = [None, Some(NoDerive(10))][0];
2319 /// match None { Some(_) => panic!("whoops"), INDEX => dbg!(INDEX), };
2327 /// Previous versions of Rust accepted constants in patterns, even if those constants' types
2328 /// did not have `PartialEq` derived. Thus the compiler falls back to runtime execution of
2329 /// `PartialEq`, which can report that two constants are not equal even if they are
2331 pub NONTRIVIAL_STRUCTURAL_MATCH,
2333 "constant used in pattern of non-structural-match type and the constant's initializer \
2334 expression contains values of non-structural-match types",
2335 @future_incompatible = FutureIncompatibleInfo {
2336 reference: "issue #73448 <https://github.com/rust-lang/rust/issues/73448>",
2341 /// The `ambiguous_associated_items` lint detects ambiguity between
2342 /// [associated items] and [enum variants].
2344 /// [associated items]: https://doc.rust-lang.org/reference/items/associated-items.html
2345 /// [enum variants]: https://doc.rust-lang.org/reference/items/enumerations.html
2349 /// ```rust,compile_fail
2356 /// fn foo() -> Self::V;
2361 /// // `Self::V` is ambiguous because it may refer to the associated type or
2362 /// // the enum variant.
2363 /// fn foo() -> Self::V { 0 }
2371 /// Previous versions of Rust did not allow accessing enum variants
2372 /// through [type aliases]. When this ability was added (see [RFC 2338]), this
2373 /// introduced some situations where it can be ambiguous what a type
2374 /// was referring to.
2376 /// To fix this ambiguity, you should use a [qualified path] to explicitly
2377 /// state which type to use. For example, in the above example the
2378 /// function can be written as `fn f() -> <Self as Tr>::V { 0 }` to
2379 /// specifically refer to the associated type.
2381 /// This is a [future-incompatible] lint to transition this to a hard
2382 /// error in the future. See [issue #57644] for more details.
2384 /// [issue #57644]: https://github.com/rust-lang/rust/issues/57644
2385 /// [type aliases]: https://doc.rust-lang.org/reference/items/type-aliases.html#type-aliases
2386 /// [RFC 2338]: https://github.com/rust-lang/rfcs/blob/master/text/2338-type-alias-enum-variants.md
2387 /// [qualified path]: https://doc.rust-lang.org/reference/paths.html#qualified-paths
2388 /// [future-incompatible]: ../index.md#future-incompatible-lints
2389 pub AMBIGUOUS_ASSOCIATED_ITEMS,
2391 "ambiguous associated items",
2392 @future_incompatible = FutureIncompatibleInfo {
2393 reference: "issue #57644 <https://github.com/rust-lang/rust/issues/57644>",
2398 /// The `soft_unstable` lint detects unstable features that were
2399 /// unintentionally allowed on stable.
2403 /// ```rust,compile_fail
2405 /// extern crate test;
2408 /// fn name(b: &mut test::Bencher) {
2417 /// The [`bench` attribute] was accidentally allowed to be specified on
2418 /// the [stable release channel]. Turning this to a hard error would have
2419 /// broken some projects. This lint allows those projects to continue to
2420 /// build correctly when [`--cap-lints`] is used, but otherwise signal an
2421 /// error that `#[bench]` should not be used on the stable channel. This
2422 /// is a [future-incompatible] lint to transition this to a hard error in
2423 /// the future. See [issue #64266] for more details.
2425 /// [issue #64266]: https://github.com/rust-lang/rust/issues/64266
2426 /// [`bench` attribute]: https://doc.rust-lang.org/nightly/unstable-book/library-features/test.html
2427 /// [stable release channel]: https://doc.rust-lang.org/book/appendix-07-nightly-rust.html
2428 /// [`--cap-lints`]: https://doc.rust-lang.org/rustc/lints/levels.html#capping-lints
2429 /// [future-incompatible]: ../index.md#future-incompatible-lints
2432 "a feature gate that doesn't break dependent crates",
2433 @future_incompatible = FutureIncompatibleInfo {
2434 reference: "issue #64266 <https://github.com/rust-lang/rust/issues/64266>",
2439 /// The `inline_no_sanitize` lint detects incompatible use of
2440 /// [`#[inline(always)]`][inline] and [`#[no_sanitize(...)]`][no_sanitize].
2442 /// [inline]: https://doc.rust-lang.org/reference/attributes/codegen.html#the-inline-attribute
2443 /// [no_sanitize]: https://doc.rust-lang.org/nightly/unstable-book/language-features/no-sanitize.html
2448 /// #![feature(no_sanitize)]
2450 /// #[inline(always)]
2451 /// #[no_sanitize(address)]
2463 /// The use of the [`#[inline(always)]`][inline] attribute prevents the
2464 /// the [`#[no_sanitize(...)]`][no_sanitize] attribute from working.
2465 /// Consider temporarily removing `inline` attribute.
2466 pub INLINE_NO_SANITIZE,
2468 "detects incompatible use of `#[inline(always)]` and `#[no_sanitize(...)]`",
2472 /// The `asm_sub_register` lint detects using only a subset of a register
2473 /// for inline asm inputs.
2477 /// ```rust,ignore (fails on non-x86_64)
2478 /// #[cfg(target_arch="x86_64")]
2479 /// use std::arch::asm;
2482 /// #[cfg(target_arch="x86_64")]
2484 /// asm!("mov {0}, {0}", in(reg) 0i16);
2489 /// This will produce:
2492 /// warning: formatting may not be suitable for sub-register argument
2493 /// --> src/main.rs:7:19
2495 /// 7 | asm!("mov {0}, {0}", in(reg) 0i16);
2496 /// | ^^^ ^^^ ---- for this argument
2498 /// = note: `#[warn(asm_sub_register)]` on by default
2499 /// = help: use the `x` modifier to have the register formatted as `ax`
2500 /// = help: or use the `r` modifier to keep the default formatting of `rax`
2505 /// Registers on some architectures can use different names to refer to a
2506 /// subset of the register. By default, the compiler will use the name for
2507 /// the full register size. To explicitly use a subset of the register,
2508 /// you can override the default by using a modifier on the template
2509 /// string operand to specify when subregister to use. This lint is issued
2510 /// if you pass in a value with a smaller data type than the default
2511 /// register size, to alert you of possibly using the incorrect width. To
2512 /// fix this, add the suggested modifier to the template, or cast the
2513 /// value to the correct size.
2515 /// See [register template modifiers] in the reference for more details.
2517 /// [register template modifiers]: https://doc.rust-lang.org/nightly/reference/inline-assembly.html#template-modifiers
2518 pub ASM_SUB_REGISTER,
2520 "using only a subset of a register for inline asm inputs",
2524 /// The `bad_asm_style` lint detects the use of the `.intel_syntax` and
2525 /// `.att_syntax` directives.
2529 /// ```rust,ignore (fails on non-x86_64)
2530 /// #[cfg(target_arch="x86_64")]
2531 /// use std::arch::asm;
2534 /// #[cfg(target_arch="x86_64")]
2538 /// "movq %{0}, %{0}", in(reg) 0usize
2544 /// This will produce:
2547 /// warning: avoid using `.att_syntax`, prefer using `options(att_syntax)` instead
2548 /// --> src/main.rs:8:14
2550 /// 8 | ".att_syntax",
2553 /// = note: `#[warn(bad_asm_style)]` on by default
2558 /// On x86, `asm!` uses the intel assembly syntax by default. While this
2559 /// can be switched using assembler directives like `.att_syntax`, using the
2560 /// `att_syntax` option is recommended instead because it will also properly
2561 /// prefix register placeholders with `%` as required by AT&T syntax.
2564 "incorrect use of inline assembly",
2568 /// The `unsafe_op_in_unsafe_fn` lint detects unsafe operations in unsafe
2569 /// functions without an explicit unsafe block.
2573 /// ```rust,compile_fail
2574 /// #![deny(unsafe_op_in_unsafe_fn)]
2576 /// unsafe fn foo() {}
2578 /// unsafe fn bar() {
2589 /// Currently, an [`unsafe fn`] allows any [unsafe] operation within its
2590 /// body. However, this can increase the surface area of code that needs
2591 /// to be scrutinized for proper behavior. The [`unsafe` block] provides a
2592 /// convenient way to make it clear exactly which parts of the code are
2593 /// performing unsafe operations. In the future, it is desired to change
2594 /// it so that unsafe operations cannot be performed in an `unsafe fn`
2595 /// without an `unsafe` block.
2597 /// The fix to this is to wrap the unsafe code in an `unsafe` block.
2599 /// This lint is "allow" by default since this will affect a large amount
2600 /// of existing code, and the exact plan for increasing the severity is
2601 /// still being considered. See [RFC #2585] and [issue #71668] for more
2604 /// [`unsafe fn`]: https://doc.rust-lang.org/reference/unsafe-functions.html
2605 /// [`unsafe` block]: https://doc.rust-lang.org/reference/expressions/block-expr.html#unsafe-blocks
2606 /// [unsafe]: https://doc.rust-lang.org/reference/unsafety.html
2607 /// [RFC #2585]: https://github.com/rust-lang/rfcs/blob/master/text/2585-unsafe-block-in-unsafe-fn.md
2608 /// [issue #71668]: https://github.com/rust-lang/rust/issues/71668
2609 pub UNSAFE_OP_IN_UNSAFE_FN,
2611 "unsafe operations in unsafe functions without an explicit unsafe block are deprecated",
2615 /// The `cenum_impl_drop_cast` lint detects an `as` cast of a field-less
2616 /// `enum` that implements [`Drop`].
2618 /// [`Drop`]: https://doc.rust-lang.org/std/ops/trait.Drop.html
2623 /// # #![allow(unused)]
2628 /// impl Drop for E {
2629 /// fn drop(&mut self) {
2630 /// println!("Drop");
2636 /// let i = e as u32;
2644 /// Casting a field-less `enum` that does not implement [`Copy`] to an
2645 /// integer moves the value without calling `drop`. This can result in
2646 /// surprising behavior if it was expected that `drop` should be called.
2647 /// Calling `drop` automatically would be inconsistent with other move
2648 /// operations. Since neither behavior is clear or consistent, it was
2649 /// decided that a cast of this nature will no longer be allowed.
2651 /// This is a [future-incompatible] lint to transition this to a hard error
2652 /// in the future. See [issue #73333] for more details.
2654 /// [future-incompatible]: ../index.md#future-incompatible-lints
2655 /// [issue #73333]: https://github.com/rust-lang/rust/issues/73333
2656 /// [`Copy`]: https://doc.rust-lang.org/std/marker/trait.Copy.html
2657 pub CENUM_IMPL_DROP_CAST,
2659 "a C-like enum implementing Drop is cast",
2660 @future_incompatible = FutureIncompatibleInfo {
2661 reference: "issue #73333 <https://github.com/rust-lang/rust/issues/73333>",
2662 reason: FutureIncompatibilityReason::FutureReleaseErrorReportNow,
2667 /// The `fuzzy_provenance_casts` lint detects an `as` cast between an integer
2673 /// #![feature(strict_provenance)]
2674 /// #![warn(fuzzy_provenance_casts)]
2677 /// let _dangling = 16_usize as *const u8;
2685 /// This lint is part of the strict provenance effort, see [issue #95228].
2686 /// Casting an integer to a pointer is considered bad style, as a pointer
2687 /// contains, besides the *address* also a *provenance*, indicating what
2688 /// memory the pointer is allowed to read/write. Casting an integer, which
2689 /// doesn't have provenance, to a pointer requires the compiler to assign
2690 /// (guess) provenance. The compiler assigns "all exposed valid" (see the
2691 /// docs of [`ptr::from_exposed_addr`] for more information about this
2692 /// "exposing"). This penalizes the optimiser and is not well suited for
2693 /// dynamic analysis/dynamic program verification (e.g. Miri or CHERI
2696 /// It is much better to use [`ptr::with_addr`] instead to specify the
2697 /// provenance you want. If using this function is not possible because the
2698 /// code relies on exposed provenance then there is as an escape hatch
2699 /// [`ptr::from_exposed_addr`].
2701 /// [issue #95228]: https://github.com/rust-lang/rust/issues/95228
2702 /// [`ptr::with_addr`]: https://doc.rust-lang.org/core/ptr/fn.with_addr
2703 /// [`ptr::from_exposed_addr`]: https://doc.rust-lang.org/core/ptr/fn.from_exposed_addr
2704 pub FUZZY_PROVENANCE_CASTS,
2706 "a fuzzy integer to pointer cast is used",
2707 @feature_gate = sym::strict_provenance;
2711 /// The `lossy_provenance_casts` lint detects an `as` cast between a pointer
2717 /// #![feature(strict_provenance)]
2718 /// #![warn(lossy_provenance_casts)]
2722 /// let _addr: usize = &x as *const u8 as usize;
2730 /// This lint is part of the strict provenance effort, see [issue #95228].
2731 /// Casting a pointer to an integer is a lossy operation, because beyond
2732 /// just an *address* a pointer may be associated with a particular
2733 /// *provenance*. This information is used by the optimiser and for dynamic
2734 /// analysis/dynamic program verification (e.g. Miri or CHERI platforms).
2736 /// Since this cast is lossy, it is considered good style to use the
2737 /// [`ptr::addr`] method instead, which has a similar effect, but doesn't
2738 /// "expose" the pointer provenance. This improves optimisation potential.
2739 /// See the docs of [`ptr::addr`] and [`ptr::expose_addr`] for more information
2740 /// about exposing pointer provenance.
2742 /// If your code can't comply with strict provenance and needs to expose
2743 /// the provenance, then there is [`ptr::expose_addr`] as an escape hatch,
2744 /// which preserves the behaviour of `as usize` casts while being explicit
2745 /// about the semantics.
2747 /// [issue #95228]: https://github.com/rust-lang/rust/issues/95228
2748 /// [`ptr::addr`]: https://doc.rust-lang.org/core/ptr/fn.addr
2749 /// [`ptr::expose_addr`]: https://doc.rust-lang.org/core/ptr/fn.expose_addr
2750 pub LOSSY_PROVENANCE_CASTS,
2752 "a lossy pointer to integer cast is used",
2753 @feature_gate = sym::strict_provenance;
2757 /// The `const_evaluatable_unchecked` lint detects a generic constant used
2763 /// const fn foo<T>() -> usize {
2764 /// if std::mem::size_of::<*mut T>() < 8 { // size of *mut T does not depend on T
2772 /// let _ = [0; foo::<T>()];
2780 /// In the 1.43 release, some uses of generic parameters in array repeat
2781 /// expressions were accidentally allowed. This is a [future-incompatible]
2782 /// lint to transition this to a hard error in the future. See [issue
2783 /// #76200] for a more detailed description and possible fixes.
2785 /// [future-incompatible]: ../index.md#future-incompatible-lints
2786 /// [issue #76200]: https://github.com/rust-lang/rust/issues/76200
2787 pub CONST_EVALUATABLE_UNCHECKED,
2789 "detects a generic constant is used in a type without a emitting a warning",
2790 @future_incompatible = FutureIncompatibleInfo {
2791 reference: "issue #76200 <https://github.com/rust-lang/rust/issues/76200>",
2796 /// The `function_item_references` lint detects function references that are
2797 /// formatted with [`fmt::Pointer`] or transmuted.
2799 /// [`fmt::Pointer`]: https://doc.rust-lang.org/std/fmt/trait.Pointer.html
2807 /// println!("{:p}", &foo);
2815 /// Taking a reference to a function may be mistaken as a way to obtain a
2816 /// pointer to that function. This can give unexpected results when
2817 /// formatting the reference as a pointer or transmuting it. This lint is
2818 /// issued when function references are formatted as pointers, passed as
2819 /// arguments bound by [`fmt::Pointer`] or transmuted.
2820 pub FUNCTION_ITEM_REFERENCES,
2822 "suggest casting to a function pointer when attempting to take references to function items",
2826 /// The `uninhabited_static` lint detects uninhabited statics.
2833 /// static EXTERN: Void;
2841 /// Statics with an uninhabited type can never be initialized, so they are impossible to define.
2842 /// However, this can be side-stepped with an `extern static`, leading to problems later in the
2843 /// compiler which assumes that there are no initialized uninhabited places (such as locals or
2844 /// statics). This was accidentally allowed, but is being phased out.
2845 pub UNINHABITED_STATIC,
2847 "uninhabited static",
2848 @future_incompatible = FutureIncompatibleInfo {
2849 reference: "issue #74840 <https://github.com/rust-lang/rust/issues/74840>",
2854 /// The `useless_deprecated` lint detects deprecation attributes with no effect.
2858 /// ```rust,compile_fail
2861 /// #[deprecated = "message"]
2862 /// impl Default for X {
2863 /// fn default() -> Self {
2873 /// Deprecation attributes have no effect on trait implementations.
2874 pub USELESS_DEPRECATED,
2876 "detects deprecation attributes with no effect",
2880 /// The `undefined_naked_function_abi` lint detects naked function definitions that
2881 /// either do not specify an ABI or specify the Rust ABI.
2886 /// #![feature(naked_functions)]
2888 /// use std::arch::asm;
2891 /// pub fn default_abi() -> u32 {
2892 /// unsafe { asm!("", options(noreturn)); }
2896 /// pub extern "Rust" fn rust_abi() -> u32 {
2897 /// unsafe { asm!("", options(noreturn)); }
2905 /// The Rust ABI is currently undefined. Therefore, naked functions should
2906 /// specify a non-Rust ABI.
2907 pub UNDEFINED_NAKED_FUNCTION_ABI,
2909 "undefined naked function ABI"
2913 /// The `ineffective_unstable_trait_impl` lint detects `#[unstable]` attributes which are not used.
2917 /// ```rust,compile_fail
2918 /// #![feature(staged_api)]
2920 /// #[derive(Clone)]
2921 /// #[stable(feature = "x", since = "1")]
2924 /// #[unstable(feature = "y", issue = "none")]
2925 /// impl Copy for S {}
2932 /// `staged_api` does not currently support using a stability attribute on `impl` blocks.
2933 /// `impl`s are always stable if both the type and trait are stable, and always unstable otherwise.
2934 pub INEFFECTIVE_UNSTABLE_TRAIT_IMPL,
2936 "detects `#[unstable]` on stable trait implementations for stable types"
2940 /// The `semicolon_in_expressions_from_macros` lint detects trailing semicolons
2941 /// in macro bodies when the macro is invoked in expression position.
2942 /// This was previous accepted, but is being phased out.
2946 /// ```rust,compile_fail
2947 /// #![deny(semicolon_in_expressions_from_macros)]
2948 /// macro_rules! foo {
2953 /// let val = match true {
2964 /// Previous, Rust ignored trailing semicolon in a macro
2965 /// body when a macro was invoked in expression position.
2966 /// However, this makes the treatment of semicolons in the language
2967 /// inconsistent, and could lead to unexpected runtime behavior
2968 /// in some circumstances (e.g. if the macro author expects
2969 /// a value to be dropped).
2971 /// This is a [future-incompatible] lint to transition this
2972 /// to a hard error in the future. See [issue #79813] for more details.
2974 /// [issue #79813]: https://github.com/rust-lang/rust/issues/79813
2975 /// [future-incompatible]: ../index.md#future-incompatible-lints
2976 pub SEMICOLON_IN_EXPRESSIONS_FROM_MACROS,
2978 "trailing semicolon in macro body used as expression",
2979 @future_incompatible = FutureIncompatibleInfo {
2980 reference: "issue #79813 <https://github.com/rust-lang/rust/issues/79813>",
2985 /// The `legacy_derive_helpers` lint detects derive helper attributes
2986 /// that are used before they are introduced.
2990 /// ```rust,ignore (needs extern crate)
2991 /// #[serde(rename_all = "camelCase")]
2992 /// #[derive(Deserialize)]
2993 /// struct S { /* fields */ }
2999 /// warning: derive helper attribute is used before it is introduced
3000 /// --> $DIR/legacy-derive-helpers.rs:1:3
3002 /// 1 | #[serde(rename_all = "camelCase")]
3005 /// 2 | #[derive(Deserialize)]
3006 /// | ----------- the attribute is introduced here
3011 /// Attributes like this work for historical reasons, but attribute expansion works in
3012 /// left-to-right order in general, so, to resolve `#[serde]`, compiler has to try to "look
3013 /// into the future" at not yet expanded part of the item , but such attempts are not always
3016 /// To fix the warning place the helper attribute after its corresponding derive.
3017 /// ```rust,ignore (needs extern crate)
3018 /// #[derive(Deserialize)]
3019 /// #[serde(rename_all = "camelCase")]
3020 /// struct S { /* fields */ }
3022 pub LEGACY_DERIVE_HELPERS,
3024 "detects derive helper attributes that are used before they are introduced",
3025 @future_incompatible = FutureIncompatibleInfo {
3026 reference: "issue #79202 <https://github.com/rust-lang/rust/issues/79202>",
3031 /// The `large_assignments` lint detects when objects of large
3032 /// types are being moved around.
3036 /// ```rust,ignore (can crash on some platforms)
3037 /// let x = [0; 50000];
3044 /// warning: moving a large value
3045 /// --> $DIR/move-large.rs:1:3
3047 /// - Copied large value here
3052 /// When using a large type in a plain assignment or in a function
3053 /// argument, idiomatic code can be inefficient.
3054 /// Ideally appropriate optimizations would resolve this, but such
3055 /// optimizations are only done in a best-effort manner.
3056 /// This lint will trigger on all sites of large moves and thus allow the
3057 /// user to resolve them in code.
3058 pub LARGE_ASSIGNMENTS,
3060 "detects large moves or copies",
3064 /// The `deprecated_cfg_attr_crate_type_name` lint detects uses of the
3065 /// `#![cfg_attr(..., crate_type = "...")]` and
3066 /// `#![cfg_attr(..., crate_name = "...")]` attributes to conditionally
3067 /// specify the crate type and name in the source code.
3072 /// #![cfg_attr(debug_assertions, crate_type = "lib")]
3080 /// The `#![crate_type]` and `#![crate_name]` attributes require a hack in
3081 /// the compiler to be able to change the used crate type and crate name
3082 /// after macros have been expanded. Neither attribute works in combination
3083 /// with Cargo as it explicitly passes `--crate-type` and `--crate-name` on
3084 /// the commandline. These values must match the value used in the source
3085 /// code to prevent an error.
3087 /// To fix the warning use `--crate-type` on the commandline when running
3088 /// rustc instead of `#![cfg_attr(..., crate_type = "...")]` and
3089 /// `--crate-name` instead of `#![cfg_attr(..., crate_name = "...")]`.
3090 pub DEPRECATED_CFG_ATTR_CRATE_TYPE_NAME,
3092 "detects usage of `#![cfg_attr(..., crate_type/crate_name = \"...\")]`",
3093 @future_incompatible = FutureIncompatibleInfo {
3094 reference: "issue #91632 <https://github.com/rust-lang/rust/issues/91632>",
3099 /// The `unexpected_cfgs` lint detects unexpected conditional compilation conditions.
3104 /// rustc --check-cfg 'names()'
3107 /// ```rust,ignore (needs command line option)
3112 /// This will produce:
3115 /// warning: unknown condition name used
3116 /// --> lint_example.rs:1:7
3118 /// 1 | #[cfg(widnows)]
3121 /// = note: `#[warn(unexpected_cfgs)]` on by default
3126 /// This lint is only active when a `--check-cfg='names(...)'` option has been passed
3127 /// to the compiler and triggers whenever an unknown condition name or value is used.
3128 /// The known condition include names or values passed in `--check-cfg`, `--cfg`, and some
3129 /// well-knows names and values built into the compiler.
3130 pub UNEXPECTED_CFGS,
3132 "detects unexpected names and values in `#[cfg]` conditions",
3136 /// The `repr_transparent_external_private_fields` lint
3137 /// detects types marked `#[repr(transparent)]` that (transitively)
3138 /// contain an external ZST type marked `#[non_exhaustive]` or containing
3143 /// ```rust,ignore (needs external crate)
3144 /// #![deny(repr_transparent_external_private_fields)]
3145 /// use foo::NonExhaustiveZst;
3147 /// #[repr(transparent)]
3148 /// struct Bar(u32, ([u32; 0], NonExhaustiveZst));
3151 /// This will produce:
3154 /// error: zero-sized fields in repr(transparent) cannot contain external non-exhaustive types
3155 /// --> src/main.rs:5:28
3157 /// 5 | struct Bar(u32, ([u32; 0], NonExhaustiveZst));
3158 /// | ^^^^^^^^^^^^^^^^
3160 /// note: the lint level is defined here
3161 /// --> src/main.rs:1:9
3163 /// 1 | #![deny(repr_transparent_external_private_fields)]
3164 /// | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3165 /// = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
3166 /// = note: for more information, see issue #78586 <https://github.com/rust-lang/rust/issues/78586>
3167 /// = note: this struct contains `NonExhaustiveZst`, which is marked with `#[non_exhaustive]`, and makes it not a breaking change to become non-zero-sized in the future.
3172 /// Previous, Rust accepted fields that contain external private zero-sized types,
3173 /// even though it should not be a breaking change to add a non-zero-sized field to
3174 /// that private type.
3176 /// This is a [future-incompatible] lint to transition this
3177 /// to a hard error in the future. See [issue #78586] for more details.
3179 /// [issue #78586]: https://github.com/rust-lang/rust/issues/78586
3180 /// [future-incompatible]: ../index.md#future-incompatible-lints
3181 pub REPR_TRANSPARENT_EXTERNAL_PRIVATE_FIELDS,
3183 "tranparent type contains an external ZST that is marked #[non_exhaustive] or contains private fields",
3184 @future_incompatible = FutureIncompatibleInfo {
3185 reference: "issue #78586 <https://github.com/rust-lang/rust/issues/78586>",
3189 declare_lint_pass! {
3190 /// Does nothing as a lint pass, but registers some `Lint`s
3191 /// that are used by other parts of the compiler.
3193 FORBIDDEN_LINT_GROUPS,
3194 ILLEGAL_FLOATING_POINT_LITERAL_PATTERN,
3195 ARITHMETIC_OVERFLOW,
3196 UNCONDITIONAL_PANIC,
3198 UNUSED_EXTERN_CRATES,
3199 UNUSED_CRATE_DEPENDENCIES,
3200 UNUSED_QUALIFICATIONS,
3202 UNFULFILLED_LINT_EXPECTATIONS,
3207 UNREACHABLE_PATTERNS,
3208 OVERLAPPING_RANGE_ENDPOINTS,
3209 BINDINGS_WITH_VARIANT_NAME,
3215 UNKNOWN_CRATE_TYPES,
3217 TRIVIAL_NUMERIC_CASTS,
3219 EXPORTED_PRIVATE_DEPENDENCIES,
3220 PUB_USE_OF_PRIVATE_EXTERN_CRATE,
3221 INVALID_TYPE_PARAM_DEFAULT,
3223 RENAMED_AND_REMOVED_LINTS,
3224 UNALIGNED_REFERENCES,
3225 CONST_ITEM_MUTATION,
3226 PATTERNS_IN_FNS_WITHOUT_BODY,
3227 MISSING_FRAGMENT_SPECIFIER,
3228 LATE_BOUND_LIFETIME_ARGUMENTS,
3229 ORDER_DEPENDENT_TRAIT_OBJECTS,
3230 COHERENCE_LEAK_CHECK,
3234 UNCONDITIONAL_RECURSION,
3235 SINGLE_USE_LIFETIMES,
3238 TYVAR_BEHIND_RAW_POINTER,
3239 ELIDED_LIFETIMES_IN_PATHS,
3241 ABSOLUTE_PATHS_NOT_STARTING_WITH_CRATE,
3242 UNSTABLE_NAME_COLLISIONS,
3243 IRREFUTABLE_LET_PATTERNS,
3244 WHERE_CLAUSES_OBJECT_SAFETY,
3245 PROC_MACRO_DERIVE_RESOLUTION_FALLBACK,
3246 MACRO_USE_EXTERN_CRATE,
3247 MACRO_EXPANDED_MACRO_EXPORTS_ACCESSED_BY_ABSOLUTE_PATHS,
3248 ILL_FORMED_ATTRIBUTE_INPUT,
3249 CONFLICTING_REPR_HINTS,
3250 META_VARIABLE_MISUSE,
3251 DEPRECATED_IN_FUTURE,
3252 AMBIGUOUS_ASSOCIATED_ITEMS,
3253 INDIRECT_STRUCTURAL_MATCH,
3254 POINTER_STRUCTURAL_MATCH,
3255 NONTRIVIAL_STRUCTURAL_MATCH,
3260 UNSAFE_OP_IN_UNSAFE_FN,
3262 CENUM_IMPL_DROP_CAST,
3263 FUZZY_PROVENANCE_CASTS,
3264 LOSSY_PROVENANCE_CASTS,
3265 CONST_EVALUATABLE_UNCHECKED,
3266 INEFFECTIVE_UNSTABLE_TRAIT_IMPL,
3269 FUNCTION_ITEM_REFERENCES,
3272 INVALID_DOC_ATTRIBUTES,
3273 SEMICOLON_IN_EXPRESSIONS_FROM_MACROS,
3274 RUST_2021_INCOMPATIBLE_CLOSURE_CAPTURES,
3275 LEGACY_DERIVE_HELPERS,
3276 PROC_MACRO_BACK_COMPAT,
3277 RUST_2021_INCOMPATIBLE_OR_PATTERNS,
3279 RUST_2021_PRELUDE_COLLISIONS,
3280 RUST_2021_PREFIXES_INCOMPATIBLE_SYNTAX,
3281 UNSUPPORTED_CALLING_CONVENTIONS,
3282 BREAK_WITH_LABEL_AND_LOOP,
3284 NON_EXHAUSTIVE_OMITTED_PATTERNS,
3285 TEXT_DIRECTION_CODEPOINT_IN_COMMENT,
3286 DEREF_INTO_DYN_SUPERTRAIT,
3287 DEPRECATED_CFG_ATTR_CRATE_TYPE_NAME,
3288 DUPLICATE_MACRO_ATTRIBUTES,
3289 SUSPICIOUS_AUTO_TRAIT_IMPLS,
3291 DEPRECATED_WHERE_CLAUSE_LOCATION,
3294 REPR_TRANSPARENT_EXTERNAL_PRIVATE_FIELDS,
3295 NAMED_ARGUMENTS_USED_POSITIONALLY,
3300 /// The `unused_doc_comments` lint detects doc comments that aren't used
3314 /// `rustdoc` does not use doc comments in all positions, and so the doc
3315 /// comment will be ignored. Try changing it to a normal comment with `//`
3316 /// to avoid the warning.
3317 pub UNUSED_DOC_COMMENTS,
3319 "detects doc comments that aren't used by rustdoc"
3323 /// The `rust_2021_incompatible_closure_captures` lint detects variables that aren't completely
3324 /// captured in Rust 2021, such that the `Drop` order of their fields may differ between
3325 /// Rust 2018 and 2021.
3327 /// It can also detect when a variable implements a trait like `Send`, but one of its fields does not,
3328 /// and the field is captured by a closure and used with the assumption that said field implements
3329 /// the same trait as the root variable.
3331 /// ### Example of drop reorder
3333 /// ```rust,compile_fail
3334 /// #![deny(rust_2021_incompatible_closure_captures)]
3335 /// # #![allow(unused)]
3337 /// struct FancyInteger(i32);
3339 /// impl Drop for FancyInteger {
3340 /// fn drop(&mut self) {
3341 /// println!("Just dropped {}", self.0);
3345 /// struct Point { x: FancyInteger, y: FancyInteger }
3348 /// let p = Point { x: FancyInteger(10), y: FancyInteger(20) };
3356 /// // ... More code ...
3364 /// In the above example, `p.y` will be dropped at the end of `f` instead of
3365 /// with `c` in Rust 2021.
3367 /// ### Example of auto-trait
3369 /// ```rust,compile_fail
3370 /// #![deny(rust_2021_incompatible_closure_captures)]
3371 /// use std::thread;
3373 /// struct Pointer(*mut i32);
3374 /// unsafe impl Send for Pointer {}
3378 /// let fptr = Pointer(&mut f as *mut i32);
3379 /// thread::spawn(move || unsafe {
3389 /// In the above example, only `fptr.0` is captured in Rust 2021.
3390 /// The field is of type `*mut i32`, which doesn't implement `Send`,
3391 /// making the code invalid as the field cannot be sent between threads safely.
3392 pub RUST_2021_INCOMPATIBLE_CLOSURE_CAPTURES,
3394 "detects closures affected by Rust 2021 changes",
3395 @future_incompatible = FutureIncompatibleInfo {
3396 reason: FutureIncompatibilityReason::EditionSemanticsChange(Edition::Edition2021),
3397 explain_reason: false,
3401 declare_lint_pass!(UnusedDocComment => [UNUSED_DOC_COMMENTS]);
3404 /// The `missing_abi` lint detects cases where the ABI is omitted from
3405 /// extern declarations.
3409 /// ```rust,compile_fail
3410 /// #![deny(missing_abi)]
3412 /// extern fn foo() {}
3419 /// Historically, Rust implicitly selected C as the ABI for extern
3420 /// declarations. We expect to add new ABIs, like `C-unwind`, in the future,
3421 /// though this has not yet happened, and especially with their addition
3422 /// seeing the ABI easily will make code review easier.
3425 "No declared ABI for extern declaration"
3429 /// The `invalid_doc_attributes` lint detects when the `#[doc(...)]` is
3434 /// ```rust,compile_fail
3435 /// #![deny(warnings)]
3437 /// pub mod submodule {
3438 /// #![doc(test(no_crate_inject))]
3446 /// Previously, there were very like checks being performed on `#[doc(..)]`
3447 /// unlike the other attributes. It'll now catch all the issues that it
3448 /// silently ignored previously.
3449 pub INVALID_DOC_ATTRIBUTES,
3451 "detects invalid `#[doc(...)]` attributes",
3452 @future_incompatible = FutureIncompatibleInfo {
3453 reference: "issue #82730 <https://github.com/rust-lang/rust/issues/82730>",
3458 /// The `proc_macro_back_compat` lint detects uses of old versions of certain
3459 /// proc-macro crates, which have hardcoded workarounds in the compiler.
3463 /// ```rust,ignore (needs-dependency)
3465 /// use time_macros_impl::impl_macros;
3467 /// impl_macros!(Foo);
3470 /// This will produce:
3473 /// warning: using an old version of `time-macros-impl`
3474 /// ::: $DIR/group-compat-hack.rs:27:5
3476 /// LL | impl_macros!(Foo);
3477 /// | ------------------ in this macro invocation
3479 /// = note: `#[warn(proc_macro_back_compat)]` on by default
3480 /// = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
3481 /// = note: for more information, see issue #83125 <https://github.com/rust-lang/rust/issues/83125>
3482 /// = note: the `time-macros-impl` crate will stop compiling in futures version of Rust. Please update to the latest version of the `time` crate to avoid breakage
3483 /// = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
3488 /// Eventually, the backwards-compatibility hacks present in the compiler will be removed,
3489 /// causing older versions of certain crates to stop compiling.
3490 /// This is a [future-incompatible] lint to ease the transition to an error.
3491 /// See [issue #83125] for more details.
3493 /// [issue #83125]: https://github.com/rust-lang/rust/issues/83125
3494 /// [future-incompatible]: ../index.md#future-incompatible-lints
3495 pub PROC_MACRO_BACK_COMPAT,
3497 "detects usage of old versions of certain proc-macro crates",
3498 @future_incompatible = FutureIncompatibleInfo {
3499 reference: "issue #83125 <https://github.com/rust-lang/rust/issues/83125>",
3500 reason: FutureIncompatibilityReason::FutureReleaseErrorReportNow,
3505 /// The `rust_2021_incompatible_or_patterns` lint detects usage of old versions of or-patterns.
3509 /// ```rust,compile_fail
3510 /// #![deny(rust_2021_incompatible_or_patterns)]
3512 /// macro_rules! match_any {
3513 /// ( $expr:expr , $( $( $pat:pat )|+ => $expr_arm:expr ),+ ) => {
3516 /// $( $pat => $expr_arm, )+
3523 /// let result: Result<i64, i32> = Err(42);
3524 /// let int: i64 = match_any!(result, Ok(i) | Err(i) => i.into());
3525 /// assert_eq!(int, 42);
3533 /// In Rust 2021, the `pat` matcher will match additional patterns, which include the `|` character.
3534 pub RUST_2021_INCOMPATIBLE_OR_PATTERNS,
3536 "detects usage of old versions of or-patterns",
3537 @future_incompatible = FutureIncompatibleInfo {
3538 reference: "<https://doc.rust-lang.org/nightly/edition-guide/rust-2021/or-patterns-macro-rules.html>",
3539 reason: FutureIncompatibilityReason::EditionError(Edition::Edition2021),
3544 /// The `rust_2021_prelude_collisions` lint detects the usage of trait methods which are ambiguous
3545 /// with traits added to the prelude in future editions.
3549 /// ```rust,compile_fail
3550 /// #![deny(rust_2021_prelude_collisions)]
3553 /// fn try_into(self) -> Result<String, !>;
3556 /// impl Foo for &str {
3557 /// fn try_into(self) -> Result<String, !> {
3558 /// Ok(String::from(self))
3563 /// let x: String = "3".try_into().unwrap();
3565 /// // This call to try_into matches both Foo:try_into and TryInto::try_into as
3566 /// // `TryInto` has been added to the Rust prelude in 2021 edition.
3567 /// println!("{x}");
3575 /// In Rust 2021, one of the important introductions is the [prelude changes], which add
3576 /// `TryFrom`, `TryInto`, and `FromIterator` into the standard library's prelude. Since this
3577 /// results in an ambiguity as to which method/function to call when an existing `try_into`
3578 /// method is called via dot-call syntax or a `try_from`/`from_iter` associated function
3579 /// is called directly on a type.
3581 /// [prelude changes]: https://blog.rust-lang.org/inside-rust/2021/03/04/planning-rust-2021.html#prelude-changes
3582 pub RUST_2021_PRELUDE_COLLISIONS,
3584 "detects the usage of trait methods which are ambiguous with traits added to the \
3585 prelude in future editions",
3586 @future_incompatible = FutureIncompatibleInfo {
3587 reference: "<https://doc.rust-lang.org/nightly/edition-guide/rust-2021/prelude.html>",
3588 reason: FutureIncompatibilityReason::EditionError(Edition::Edition2021),
3593 /// The `rust_2021_prefixes_incompatible_syntax` lint detects identifiers that will be parsed as a
3594 /// prefix instead in Rust 2021.
3598 /// ```rust,edition2018,compile_fail
3599 /// #![deny(rust_2021_prefixes_incompatible_syntax)]
3601 /// macro_rules! m {
3602 /// (z $x:expr) => ();
3612 /// In Rust 2015 and 2018, `z"hey"` is two tokens: the identifier `z`
3613 /// followed by the string literal `"hey"`. In Rust 2021, the `z` is
3614 /// considered a prefix for `"hey"`.
3616 /// This lint suggests to add whitespace between the `z` and `"hey"` tokens
3617 /// to keep them separated in Rust 2021.
3618 // Allow this lint -- rustdoc doesn't yet support threading edition into this lint's parser.
3619 #[allow(rustdoc::invalid_rust_codeblocks)]
3620 pub RUST_2021_PREFIXES_INCOMPATIBLE_SYNTAX,
3622 "identifiers that will be parsed as a prefix in Rust 2021",
3623 @future_incompatible = FutureIncompatibleInfo {
3624 reference: "<https://doc.rust-lang.org/nightly/edition-guide/rust-2021/reserving-syntax.html>",
3625 reason: FutureIncompatibilityReason::EditionError(Edition::Edition2021),
3631 /// The `unsupported_calling_conventions` lint is output whenever there is a use of the
3632 /// `stdcall`, `fastcall`, `thiscall`, `vectorcall` calling conventions (or their unwind
3633 /// variants) on targets that cannot meaningfully be supported for the requested target.
3635 /// For example `stdcall` does not make much sense for a x86_64 or, more apparently, powerpc
3636 /// code, because this calling convention was never specified for those targets.
3638 /// Historically MSVC toolchains have fallen back to the regular C calling convention for
3639 /// targets other than x86, but Rust doesn't really see a similar need to introduce a similar
3640 /// hack across many more targets.
3644 /// ```rust,ignore (needs specific targets)
3645 /// extern "stdcall" fn stdcall() {}
3648 /// This will produce:
3651 /// warning: use of calling convention not supported on this target
3652 /// --> $DIR/unsupported.rs:39:1
3654 /// LL | extern "stdcall" fn stdcall() {}
3655 /// | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3657 /// = note: `#[warn(unsupported_calling_conventions)]` on by default
3658 /// = warning: this was previously accepted by the compiler but is being phased out;
3659 /// it will become a hard error in a future release!
3660 /// = note: for more information, see issue ...
3665 /// On most of the targets the behaviour of `stdcall` and similar calling conventions is not
3666 /// defined at all, but was previously accepted due to a bug in the implementation of the
3668 pub UNSUPPORTED_CALLING_CONVENTIONS,
3670 "use of unsupported calling convention",
3671 @future_incompatible = FutureIncompatibleInfo {
3672 reference: "issue #87678 <https://github.com/rust-lang/rust/issues/87678>",
3677 /// The `break_with_label_and_loop` lint detects labeled `break` expressions with
3678 /// an unlabeled loop as their value expression.
3684 /// break 'label loop { break 42; };
3692 /// In Rust, loops can have a label, and `break` expressions can refer to that label to
3693 /// break out of specific loops (and not necessarily the innermost one). `break` expressions
3694 /// can also carry a value expression, which can be another loop. A labeled `break` with an
3695 /// unlabeled loop as its value expression is easy to confuse with an unlabeled break with
3696 /// a labeled loop and is thus discouraged (but allowed for compatibility); use parentheses
3697 /// around the loop expression to silence this warning. Unlabeled `break` expressions with
3698 /// labeled loops yield a hard error, which can also be silenced by wrapping the expression
3700 pub BREAK_WITH_LABEL_AND_LOOP,
3702 "`break` expression with label and unlabeled loop as value expression"
3706 /// The `non_exhaustive_omitted_patterns` lint detects when a wildcard (`_` or `..`) in a
3707 /// pattern for a `#[non_exhaustive]` struct or enum is reachable.
3711 /// ```rust,ignore (needs separate crate)
3713 /// #[non_exhaustive]
3716 /// B, // added variant in non breaking change
3720 /// #![feature(non_exhaustive_omitted_patterns_lint)]
3724 /// #[warn(non_exhaustive_omitted_patterns)]
3729 /// This will produce:
3732 /// warning: reachable patterns not covered of non exhaustive enum
3733 /// --> $DIR/reachable-patterns.rs:70:9
3736 /// | ^ pattern `B` not covered
3738 /// note: the lint level is defined here
3739 /// --> $DIR/reachable-patterns.rs:69:16
3741 /// LL | #[warn(non_exhaustive_omitted_patterns)]
3742 /// | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3743 /// = help: ensure that all possible cases are being handled by adding the suggested match arms
3744 /// = note: the matched value is of type `Bar` and the `non_exhaustive_omitted_patterns` attribute was found
3749 /// Structs and enums tagged with `#[non_exhaustive]` force the user to add a
3750 /// (potentially redundant) wildcard when pattern-matching, to allow for future
3751 /// addition of fields or variants. The `non_exhaustive_omitted_patterns` lint
3752 /// detects when such a wildcard happens to actually catch some fields/variants.
3753 /// In other words, when the match without the wildcard would not be exhaustive.
3754 /// This lets the user be informed if new fields/variants were added.
3755 pub NON_EXHAUSTIVE_OMITTED_PATTERNS,
3757 "detect when patterns of types marked `non_exhaustive` are missed",
3758 @feature_gate = sym::non_exhaustive_omitted_patterns_lint;
3762 /// The `text_direction_codepoint_in_comment` lint detects Unicode codepoints in comments that
3763 /// change the visual representation of text on screen in a way that does not correspond to
3764 /// their on memory representation.
3768 /// ```rust,compile_fail
3769 /// #![deny(text_direction_codepoint_in_comment)]
3771 /// println!("{:?}"); // '‮');
3779 /// Unicode allows changing the visual flow of text on screen in order to support scripts that
3780 /// are written right-to-left, but a specially crafted comment can make code that will be
3781 /// compiled appear to be part of a comment, depending on the software used to read the code.
3782 /// To avoid potential problems or confusion, such as in CVE-2021-42574, by default we deny
3784 pub TEXT_DIRECTION_CODEPOINT_IN_COMMENT,
3786 "invisible directionality-changing codepoints in comment"
3790 /// The `deref_into_dyn_supertrait` lint is output whenever there is a use of the
3791 /// `Deref` implementation with a `dyn SuperTrait` type as `Output`.
3793 /// These implementations will become shadowed when the `trait_upcasting` feature is stabilized.
3794 /// The `deref` functions will no longer be called implicitly, so there might be behavior change.
3798 /// ```rust,compile_fail
3799 /// #![deny(deref_into_dyn_supertrait)]
3800 /// #![allow(dead_code)]
3802 /// use core::ops::Deref;
3806 /// impl<'a> Deref for dyn 'a + B {
3807 /// type Target = dyn A;
3808 /// fn deref(&self) -> &Self::Target {
3813 /// fn take_a(_: &dyn A) { }
3815 /// fn take_b(b: &dyn B) {
3824 /// The dyn upcasting coercion feature adds new coercion rules, taking priority
3825 /// over certain other coercion rules, which will cause some behavior change.
3826 pub DEREF_INTO_DYN_SUPERTRAIT,
3828 "`Deref` implementation usage with a supertrait trait object for output might be shadowed in the future",
3829 @future_incompatible = FutureIncompatibleInfo {
3830 reference: "issue #89460 <https://github.com/rust-lang/rust/issues/89460>",
3835 /// The `duplicate_macro_attributes` lint detects when a `#[test]`-like built-in macro
3836 /// attribute is duplicated on an item. This lint may trigger on `bench`, `cfg_eval`, `test`
3837 /// and `test_case`.
3841 /// ```rust,ignore (needs --test)
3847 /// This will produce:
3850 /// warning: duplicated attribute
3851 /// --> src/lib.rs:2:1
3856 /// = note: `#[warn(duplicate_macro_attributes)]` on by default
3861 /// A duplicated attribute may erroneously originate from a copy-paste and the effect of it
3862 /// being duplicated may not be obvious or desirable.
3864 /// For instance, doubling the `#[test]` attributes registers the test to be run twice with no
3865 /// change to its environment.
3867 /// [issue #90979]: https://github.com/rust-lang/rust/issues/90979
3868 pub DUPLICATE_MACRO_ATTRIBUTES,
3870 "duplicated attribute"
3874 /// The `suspicious_auto_trait_impls` lint checks for potentially incorrect
3875 /// implementations of auto traits.
3880 /// struct Foo<T>(T);
3882 /// unsafe impl<T> Send for Foo<*const T> {}
3889 /// A type can implement auto traits, e.g. `Send`, `Sync` and `Unpin`,
3890 /// in two different ways: either by writing an explicit impl or if
3891 /// all fields of the type implement that auto trait.
3893 /// The compiler disables the automatic implementation if an explicit one
3894 /// exists for given type constructor. The exact rules governing this
3895 /// are currently unsound and quite subtle and and will be modified in the future.
3896 /// This change will cause the automatic implementation to be disabled in more
3897 /// cases, potentially breaking some code.
3898 pub SUSPICIOUS_AUTO_TRAIT_IMPLS,
3900 "the rules governing auto traits will change in the future",
3901 @future_incompatible = FutureIncompatibleInfo {
3902 reason: FutureIncompatibilityReason::FutureReleaseSemanticsChange,
3903 reference: "issue #93367 <https://github.com/rust-lang/rust/issues/93367>",
3908 /// The `deprecated_where_clause_location` lint detects when a where clause in front of the equals
3909 /// in an associated type.
3914 /// #![feature(generic_associated_types)]
3917 /// type Assoc<'a> where Self: 'a;
3920 /// impl Trait for () {
3921 /// type Assoc<'a> where Self: 'a = ();
3929 /// The preferred location for where clauses on associated types in impls
3930 /// is after the type. However, for most of generic associated types development,
3931 /// it was only accepted before the equals. To provide a transition period and
3932 /// further evaluate this change, both are currently accepted. At some point in
3933 /// the future, this may be disallowed at an edition boundary; but, that is
3934 /// undecided currently.
3935 pub DEPRECATED_WHERE_CLAUSE_LOCATION,
3937 "deprecated where clause location"
3941 /// The `test_unstable_lint` lint tests unstable lints and is perma-unstable.
3946 /// #![allow(test_unstable_lint)]
3953 /// In order to test the behavior of unstable lints, a permanently-unstable
3954 /// lint is required. This lint can be used to trigger warnings and errors
3955 /// from the compiler related to unstable lints.
3956 pub TEST_UNSTABLE_LINT,
3958 "this unstable lint is only for testing",
3959 @feature_gate = sym::test_unstable_lint;
3963 /// The `ffi_unwind_calls` lint detects calls to foreign functions or function pointers with
3964 /// `C-unwind` or other FFI-unwind ABIs.
3968 /// ```rust,ignore (need FFI)
3969 /// #![feature(ffi_unwind_calls)]
3970 /// #![feature(c_unwind)]
3974 /// # pub fn "C-unwind" fn foo() {}
3977 /// extern "C-unwind" {
3982 /// unsafe { foo(); }
3983 /// let ptr: unsafe extern "C-unwind" fn() = foo;
3984 /// unsafe { ptr(); }
3992 /// For crates containing such calls, if they are compiled with `-C panic=unwind` then the
3993 /// produced library cannot be linked with crates compiled with `-C panic=abort`. For crates
3994 /// that desire this ability it is therefore necessary to avoid such calls.
3995 pub FFI_UNWIND_CALLS,
3997 "call to foreign functions or function pointers with FFI-unwind ABI",
3998 @feature_gate = sym::c_unwind;
4002 /// The `named_arguments_used_positionally` lint detects cases where named arguments are only
4003 /// used positionally in format strings. This usage is valid but potentially very confusing.
4007 /// ```rust,compile_fail
4008 /// #![deny(named_arguments_used_positionally)]
4011 /// println!("{}", _x = 1); // Prints 1, will trigger lint
4013 /// println!("{}", _x); // Prints 5, no lint emitted
4014 /// println!("{_x}", _x = _x); // Prints 5, no lint emitted
4022 /// Rust formatting strings can refer to named arguments by their position, but this usage is
4023 /// potentially confusing. In particular, readers can incorrectly assume that the declaration
4024 /// of named arguments is an assignment (which would produce the unit type).
4025 /// For backwards compatibility, this is not a hard error.
4026 pub NAMED_ARGUMENTS_USED_POSITIONALLY,
4028 "named arguments in format used positionally"