Fix compilation error/warn #27365
Merged
Fix compilation error/warn #27365
Conversation
This file contains 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
There is a compile error in ft_motion.cpp by using arm-none-eabi-g++ of PlatformIO Core 6.1.15 on Windows 11. The error message is:
The error occurs at scalar initializer
{ 0 }. I think braced scalar initializers are valid. However, the g++ reported an error. Maybe other versions of g++ may warn.Other scalar initializers in ft_motion.cpp are not braced. I think it is good to unify by using the same syntax. This PR unbrace two scalar initializers.
note:
I found @yunline also commented on the same error below. But suggested code was not included in the merge. This PR and @yunline's code are the same.
Requirements
Benefits
Configurations
Related Issues