Repository navigation
Apply fixes found by Fortitude linter - #13
Merged
Merged
Conversation
nusbaume
marked this pull request as ready for review
August 27, 2026 15:21
peverwhee
approved these changes
Aug 27, 2026
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
2 participants
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 PR makes modifications in order to fix/resolve most of the issues found by applying the Fortitude linter. There are a few errors that still exist (e.g. cyclomatic complexity) that would be good to resolve later, but will require more design effort.
Also note that Fortitude was only applied to the
srcdirectory. Everything undertestwas left as-is.Finally, some code changes were made with Claude Opus 5.
Tests run:
Successfully passed all SIMA GNU and Intel regression tests with no failures or differences reported.