Std occurs in tests in no_std crate

What is it you're trying to show?

1 Like

same function failed in unit_test, but passed in integrate tests. libm::exp is not used as expected.

std::primitive::f32::exp is incorrectly used in tests, even this is a embeded crate with the #![no_std] attribute, which causes Exp::exp(4_32) != 4_32.exp()

Please post code and errors as text, not images.

Integration tests always run with libstd available as the test harness itself depends on libstd for everything from spawning threads to printing results and getting the commandline arguments.

4 Likes