Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: remove clippy unexpected_cfgs warning #1588

Merged
merged 1 commit into from
May 21, 2024

Conversation

Daniel-Aaron-Bloom
Copy link
Contributor

Since std doesn't exist as a cfg, not(std) was always true, so this does not change any behavior.

warning: unexpected `cfg` condition name: `std`
 --> maybe_rayon/src/lib.rs:1:17
  |
1 | #![cfg_attr(not(std), no_std)]
  |                 ^^^
  |
  = 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`, `windows`
  = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(std)");` to the top of the `build.rs`
  = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
  = note: `#[warn(unexpected_cfgs)]` on by default

Since `std` doesn't exist as a cfg, `not(std)` was always true, so this does not change any behavior.
@Nashtare Nashtare merged commit 430290f into 0xPolygonZero:main May 21, 2024
4 checks passed
@Daniel-Aaron-Bloom Daniel-Aaron-Bloom deleted the dbloom/no-std branch May 22, 2024 16:22
hratoanina pushed a commit that referenced this pull request Jul 16, 2024
Since `std` doesn't exist as a cfg, `not(std)` was always true, so this does not change any behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants