Add rubicon 3.x support #7
clippy
10 errors
Details
Results
Message level | Amount |
---|---|
Internal compiler error | 0 |
Error | 10 |
Warning | 0 |
Note | 0 |
Help | 0 |
Versions
- rustc 1.80.0 (051478957 2024-07-21)
- cargo 1.80.0 (376290515 2024-07-16)
- clippy 0.1.80 (0514789 2024-07-21)
Annotations
Check failure on line 462 in tracing-core/src/dispatcher.rs
github-actions / clippy
creating a shared reference to mutable static is discouraged
error: creating a shared reference to mutable static is discouraged
--> tracing-core/src/dispatcher.rs:462:9
|
462 | &GLOBAL_DISPATCH
| ^^^^^^^^^^^^^^^^ shared reference to mutable static
|
= note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
= note: this will be a hard error in the 2024 edition
= note: this shared reference has lifetime `'static`, but if the static ever gets mutated, or a mutable reference is created, then any further use of this shared reference is Undefined Behavior
= note: `-D static-mut-refs` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(static_mut_refs)]`
help: use `addr_of!` instead to create a raw pointer
|
462 | addr_of!(GLOBAL_DISPATCH)
|
Check failure on line 841 in tracing-core/src/field.rs
github-actions / clippy
bound is defined in more than one place
error: bound is defined in more than one place
--> tracing-core/src/field.rs:841:18
|
841 | pub fn field<Q: ?Sized>(&self, name: &Q) -> Option<Field>
| ^
842 | where
843 | Q: Borrow<str>,
| ^
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#multiple_bound_locations
= note: `-D clippy::multiple-bound-locations` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::multiple_bound_locations)]`
Check failure on line 270 in tracing-core/src/field.rs
github-actions / clippy
unexpected `cfg` condition name: `tracing_unstable`
error: unexpected `cfg` condition name: `tracing_unstable`
--> tracing-core/src/field.rs:270:15
|
270 | #[cfg(all(tracing_unstable, feature = "valuable"))]
| ^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tracing_unstable)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tracing_unstable)");` to the top of the `build.rs`
= note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
Check failure on line 735 in tracing-core/src/field.rs
github-actions / clippy
unexpected `cfg` condition name: `tracing_unstable`
error: unexpected `cfg` condition name: `tracing_unstable`
--> tracing-core/src/field.rs:735:11
|
735 | #[cfg(all(tracing_unstable, feature = "valuable"))]
| ^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tracing_unstable)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tracing_unstable)");` to the top of the `build.rs`
= note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
Check failure on line 732 in tracing-core/src/field.rs
github-actions / clippy
unexpected `cfg` condition name: `tracing_unstable`
error: unexpected `cfg` condition name: `tracing_unstable`
--> tracing-core/src/field.rs:732:11
|
732 | #[cfg(all(tracing_unstable, feature = "valuable"))]
| ^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tracing_unstable)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tracing_unstable)");` to the top of the `build.rs`
= note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
Check failure on line 724 in tracing-core/src/field.rs
github-actions / clippy
unexpected `cfg` condition name: `tracing_unstable`
error: unexpected `cfg` condition name: `tracing_unstable`
--> tracing-core/src/field.rs:724:11
|
724 | #[cfg(all(tracing_unstable, feature = "valuable"))]
| ^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tracing_unstable)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tracing_unstable)");` to the top of the `build.rs`
= note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
Check failure on line 721 in tracing-core/src/field.rs
github-actions / clippy
unexpected `cfg` condition name: `tracing_unstable`
error: unexpected `cfg` condition name: `tracing_unstable`
--> tracing-core/src/field.rs:721:11
|
721 | #[cfg(all(tracing_unstable, feature = "valuable"))]
| ^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tracing_unstable)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tracing_unstable)");` to the top of the `build.rs`
= note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
Check failure on line 374 in tracing-core/src/field.rs
github-actions / clippy
unexpected `cfg` condition name: `tracing_unstable`
error: unexpected `cfg` condition name: `tracing_unstable`
--> tracing-core/src/field.rs:374:11
|
374 | #[cfg(all(tracing_unstable, feature = "valuable"))]
| ^^^^^^^^^^^^^^^^
|
= help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tracing_unstable)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tracing_unstable)");` to the top of the `build.rs`
= note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
Check failure on line 150 in tracing-core/src/dispatcher.rs
github-actions / clippy
unexpected `cfg` condition value: `alloc`
error: unexpected `cfg` condition value: `alloc`
--> tracing-core/src/dispatcher.rs:150:7
|
150 | #[cfg(feature = "alloc")]
| ^^^^^^^^^^^^^^^^^
|
= note: expected values for `feature` are: `default`, `once_cell`, `std`, and `valuable`
= help: consider adding `alloc` as a feature in `Cargo.toml`
= note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
Check failure on line 147 in tracing-core/src/dispatcher.rs
github-actions / clippy
unexpected `cfg` condition value: `alloc`
error: unexpected `cfg` condition value: `alloc`
--> tracing-core/src/dispatcher.rs:147:7
|
147 | #[cfg(feature = "alloc")]
| ^^^^^^^^^^^^^^^^^
|
= note: expected values for `feature` are: `default`, `once_cell`, `std`, and `valuable`
= help: consider adding `alloc` as a feature in `Cargo.toml`
= note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
= note: `-D unexpected-cfgs` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(unexpected_cfgs)]`