I believe it's possible to accidentally break downstream consumers of a supposedly no_std crate by adding a dependency that is not itself no_std. Prevent this with a check on GitHub actions. This can be done with cargo nono check, or perhaps a no_std test crate.
casey
commented
4 years ago
I believe it's possible to accidentally break downstream consumers of a supposedly
no_stdcrate by adding a dependency that is not itselfno_std. Prevent this with a check on GitHub actions. This can be done withcargo nono check, or perhaps ano_stdtest crate.