| Crates.io | aleph-zero-cargo-nono |
| lib.rs | aleph-zero-cargo-nono |
| version | 0.1.9 |
| created_at | 2023-03-27 07:18:00.041514+00 |
| updated_at | 2023-03-27 07:18:00.041514+00 |
| description | Detect (possible) no_std compatibility of your crate and dependencies |
| homepage | |
| repository | https://github.com/hobofan/cargo-nono |
| max_upload_size | |
| id | 821888 |
| size | 78,686 |
From embedded programming, over smart contracts in Rust, to general cross-platform portable crates, #![no_std] crates are becoming more and more widespread.
However it is currently a very cumbersome process to find out if and why (not) a crate is compatible with no_std usage, and often requires a lengthy trial and error process, and digging through the source of all your dependencies.
cargo nono tries to aid you in navigating the current minefield that is no_std usage, and it's biggest "no no"s.
cargo-nono also comes as prebuilt binaries (useful for CI):
curl -LSfs https://japaric.github.io/trust/install.sh | \
sh -s -- --git hobofan/cargo-nono
cargo install cargo-nono
# For warnings with more informative messages install like this
RUSTFLAGS="--cfg procmacro2_semver_exempt" cargo install cargo-nono
Run in the crate directory you want to check:
cargo nono check
The cargo nono check subcommand also understands the --no-default-features and --features <FEATURES> flags to help in conditional no_std setups.
no_std compatibility in dependencies by looking for a #![no_std] attribute or the often used conditional #![cfg_attr(not(feature = "std"), no_std)]std feature flagsuse std:: statements in code[build-dependencies] features bleeding over: cargo#5730Licensed under either of
at your option.