Update no_atomic.rs and fix CI failures #129
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
update-no-atomic-rs
branch
from
a4d7990
to
0518498
Compare
```
error: struct `S` is never constructed
--> tests/tests/derive.rs:49:12
|
49 | struct S {
| ^
|
= note: `-D dead-code` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(dead_code)]`
error: enum `E` is never used
--> tests/tests/derive.rs:54:10
|
54 | enum E {
| ^
error: struct `Test` is never constructed
--> tests/tests/derive.rs:59:12
|
59 | struct Test<'a> {
| ^^^^
```
```
error: unexpected `cfg` condition name: `valuable_no_atomic_cas`
--> valuable/src/enumerable.rs:640:15
|
640 | #[cfg(not(valuable_no_atomic_cas))]
| ^^^^^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic_cas)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic_cas)");` 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
= note: `-D unexpected-cfgs` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(unexpected_cfgs)]`
error: unexpected `cfg` condition name: `valuable_no_atomic_cas`
--> valuable/src/listable.rs:128:15
|
128 | #[cfg(not(valuable_no_atomic_cas))]
| ^^^^^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic_cas)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic_cas)");` 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
error: unexpected `cfg` condition name: `valuable_no_atomic_cas`
--> valuable/src/listable.rs:168:15
|
168 | #[cfg(not(valuable_no_atomic_cas))]
| ^^^^^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic_cas)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic_cas)");` 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
error: unexpected `cfg` condition name: `valuable_no_atomic_cas`
--> valuable/src/mappable.rs:126:15
|
126 | #[cfg(not(valuable_no_atomic_cas))]
| ^^^^^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic_cas)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic_cas)");` 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
error: unexpected `cfg` condition name: `valuable_no_atomic_cas`
--> valuable/src/structable.rs:493:15
|
493 | #[cfg(not(valuable_no_atomic_cas))]
| ^^^^^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic_cas)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic_cas)");` 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
error: unexpected `cfg` condition name: `valuable_no_atomic_cas`
--> valuable/src/tuplable.rs:136:15
|
136 | #[cfg(not(valuable_no_atomic_cas))]
| ^^^^^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic_cas)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic_cas)");` 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
error: unexpected `cfg` condition name: `valuable_no_atomic`
--> valuable/src/valuable.rs:190:11
|
190 | #[cfg(not(valuable_no_atomic))]
| ^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic)");` 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
error: unexpected `cfg` condition name: `valuable_no_atomic`
--> valuable/src/valuable.rs:216:11
|
216 | #[cfg(not(valuable_no_atomic))]
| ^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic)");` 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
error: unexpected `cfg` condition name: `valuable_no_atomic_cas`
--> valuable/src/valuable.rs:104:15
|
104 | #[cfg(not(valuable_no_atomic_cas))]
| ^^^^^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic_cas)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic_cas)");` 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
error: unexpected `cfg` condition name: `valuable_no_atomic_64`
--> valuable/src/valuable.rs:222:15
|
222 | #[cfg(not(valuable_no_atomic_64))]
| ^^^^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic_64)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic_64)");` 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
error: unexpected `cfg` condition name: `valuable_no_atomic_64`
--> valuable/src/valuable.rs:228:15
|
228 | #[cfg(not(valuable_no_atomic_64))]
| ^^^^^^^^^^^^^^^^^^^^^
|
= 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(valuable_no_atomic_64)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(valuable_no_atomic_64)");` 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
```
taiki-e
approved these changes
Jul 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Auto-generated by create-pull-request
Please close and immediately reopen this pull request to run CI.