Hotfix/Compiler Warnings MuJocO#989
Merged
Merged
Conversation
Contributor
Implicit conversion raises warnings
Contributor
Author
Contributor
Author
Contributor
|
Cool, thanks for addressing these warnings. Yesterday I was not able to build BSK+mujoco in Xcode, after your commits earlier today it works again. This gives us a clean code base to work with 🤠 |
Contributor
Author
|
@schaubh ready for review. I don't see any compiler warnings on the Macos build. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.


Description
Some
mujocoDynamicscode was raising compiler warnings. These commits address these.One of the warnings was due to a missing override keyword.
The other warning was raised because some functions were reaching the control flow end without returning the expected value. However, this is because a
logAndThrowwas being called, which throws an error and thus interrupts normal control flow. By letting the compiler know that this function is[[noreturn]], it no longer cares about the return on that path of the control flow.Verification
I'll check the MacOS build logs for compiler warnings (I'm tagging this PR dont merge until I've done this manual check).