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.
Added
#[must_use]
to those methods which look like(&*self ...) -> Self
(basically methods which take a self by non-mutable ref or by value, and which return a Self). However, I did not add such bounds to trait impls whose trait definition already had such amust_use
on it (all the core::ops and all the From impls). Along those notes, I added[#must_use]
toFloatExt
's trait definition.On this (m1 mac), most of the tests except for those in "euler::quat::test_" did not work on main currently and after this, continue to not work. It appears that they work fine on the Github Actions runner, so I suspect that this PR should be fine, since this should not result in any different code generated.
I tried to check all the Tera files as appropriate, and I think I got them all, but even if I didn't, I would be comfortable with this PR merging, as it's just a continuation of efforts to match the std's new
must_use
style.