cargo-nono
cargo-nono copied to clipboard
hobofan
Check your crate for (possible) no_std compatibility
If a crate has ``` #[cfg(feature = "std")] use std::vec::Vec; ``` this shouldn't result in FAILURE because the compiler switch deactivates the `use std::`
if run in an empty directory it panics: ``` thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error("EOF while parsing a value", line: 1, column: 0)', /home/cargo-nono-0.1.9/src/util.rs:19:45 note:...
A crate with `#![cfg_attr(not(any(test, doctest)), no_std)]` definitely does not need std for it to be used, although it uses std for some of its own tests. Is there any reason...
[rustc-std-workspace-core](https://crates.io/crates/rustc-std-workspace-core) is an explicitly empty crate used by some low-level no_std crates in the Rust ecosystem, such as libc, when the rustc-dep-of-std feature is enabled. It's completely empty, so it...
While there are still crates whose no_std status isn't correctly determined, it's useful to be able manually allow specific crates that are known to be no_std.
Since the checks rely on currently somewhat limited mechanisms, it's probably a good idea to start compiling a list of where the checks yield wrong results. This then allows us...
Running `cargo nono` on my crate [hmmm](https://github.com/paulkernfeld/hmmm), it produced useful output but it also looks like it crashed. ``` (base) [13:27:101]% RUST_BACKTRACE=full cargo nono check paul@compy386:~/projects/hmmm on master -> origin/master...
A fairly common pattern in `no_std`-compatible projects is to put this in your `lib.rs` file: ```rust extern crate core as std; ``` … which allows you to then keep using...
All the recent CI builds have been failing on Linux. The most obvious thing that changes since the last build that were green, is the upgrade from Rust 1.32.0 ->...