Check no_std compatibility in CI and fix remaining use of std
#9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
It can be easy to accidentally break
no_stdcompatibility. We should check it in CI!We're also missing some
f32method lints inclippy.toml, and are still actually usingstd::f32::roundin one place.Solution
Add
no_stdchecks to CI, and add the remainingf32method lints toclippy.toml. Through this I also discovered that we need acritical-sectionfeature for Bevy in someno_stdenvironments.The check is based on
no_stdlibrary example.