Closed BurntSushi closed 3 weeks ago
I was lured into a false sense of confidence with CI testing. Because tests unconditionally enable std, this
std
cargo test --lib --no-default-features --features alloc
doesn't actually fail when there is an errant std reference. But this does:
cargo build --no-default-features --features alloc
We fix our test script to catch this case and also fix the build errors.
test
Fixes #108
I was lured into a false sense of confidence with CI testing. Because tests unconditionally enable
std
, thisdoesn't actually fail when there is an errant
std
reference. But this does:We fix our
test
script to catch this case and also fix the build errors.Fixes #108