We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
extern crate core as std;
A fairly common pattern in no_std-compatible projects is to put this in your lib.rs file:
no_std
lib.rs
… which allows you to then keep using use std::…, instead of having to use use core::….
use std::…
use core::…
Running $ cargo nono check on the lazycell crate, which uses aforementioned trick produces the following errors:
$ cargo nono check
lazycell
❯ cargo nono check lazycell: ❌ - Source code contains an explicit `use std::` statement. --> src/lib.rs - Source code contains an explicit `use std::` statement. --> src/lib.rs - Source code contains an explicit `use std::` statement. --> src/lib.rs - Source code contains an explicit `use std::` statement. --> src/lib.rs - Source code contains an explicit `use std::` statement. --> src/lib.rs - Source code contains an explicit `use std::` statement. --> src/lib.rs
… even though the crate is safe to use for no_std.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A fairly common pattern in
no_std
-compatible projects is to put this in yourlib.rs
file:… which allows you to then keep using
use std::…
, instead of having to useuse core::…
.Running
$ cargo nono check
on thelazycell
crate, which uses aforementioned trick produces the following errors:… even though the crate is safe to use for
no_std
.The text was updated successfully, but these errors were encountered: