In #206 we removed the no_std test added in #204 to be able to publish 0.10.2. We should reintroduce the test to make sure we don't break no_std unexpectedly going forward.
Note that this is the second time we've had to remove a no_std test suite because it was failing too often for reasons that are outside the scope of this crate.
In #206 we removed the
no_std
test added in #204 to be able to publish 0.10.2. We should reintroduce the test to make sure we don't breakno_std
unexpectedly going forward.Note that this is the second time we've had to remove a
no_std
test suite because it was failing too often for reasons that are outside the scope of this crate.