You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently wrote a few lints for clippy that should help with CI testing given the couple of "fix no_std" pull requests I've seen: rust-lang/rust-clippy#9103
Although I don't think these are going to be stable until Rust 1.64
The text was updated successfully, but these errors were encountered:
i don't think there've been any no-std pull requests, but some commits if that's what you're thinking? in that case it was kind of mislabeled - i expect the crate to build with no features, so "no_std" (in a minimal sense) is cargo build --no-default-features. that didn't work for mundane reason about the fmt feature, but all did at least get std/core right. even then, cargo build --no-default-features --features "fmt" did work, i believe.. that said, doc comments do reference std::fmt::* because (iirc?) those can't be made to build no-std even if i wanted...
either way i'm super down for std_instead_of_core as a lint! though i rarely run clippy myself. yaxpeax-x86 using alloc would almost certainly be a bug though 😁
I recently wrote a few lints for clippy that should help with CI testing given the couple of "fix no_std" pull requests I've seen: rust-lang/rust-clippy#9103
Although I don't think these are going to be stable until Rust 1.64
The text was updated successfully, but these errors were encountered: