style: Format sources using astyle 3.0.1 #515
Closed
Conversation
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
This change applies code formatting to the source files using astyle version 3.0.1 according to the project's style guidelines. Changes are purely stylistic with no functional modifications.
|
cc: @danmar |
it just creates extra stylistic changes in the git log. when we move to uncrustify we'll probably need to do something like this again. |
|
Thanks for taking the time to follow up 🙏 Looking forward to the improved code formatting infrastructure. If possible consider:
I should have specified that this type of changes should be added to |
This was referenced Aug 28, 2025
Merged
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.
This pull request reformats the codebase using astyle 3.0.1 to ensure consistency with the project’s current style guidelines.
Context
As noted in the review (#508 (comment)), the long-term plan is to transition formatting to uncrustify (likely by adapting the
runformatscript from the cppcheck repo). While that transition is being worked out, this change helps keep the repository consistent and avoids confusion for contributors.