Skip to content

Issues: PlasmaFAIR/fortitude

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

82 Open 104 Closed
82 Open 104 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Unsafe fix is flagged as fixable in --statistics bug Something isn't working
#367 opened Mar 14, 2025 by MatthAlex
.eqv. and .neqv. should be used to compare logical variables, not == and /= rule A new rule for the linter
#366 opened Mar 14, 2025 by Beliavsky
1
Array indices should not be reals
#365 opened Mar 14, 2025 by Beliavsky
Using fortitude with the fypp preprocessor enhancement New feature or request
#356 opened Mar 8, 2025 by rhdtownsend
1
Add --target-std flag configuration Related to settings and configuration enhancement New feature or request
#353 opened Mar 7, 2025 by LiamPattinson
2
bug in [S061] bug Something isn't working
#347 opened Mar 4, 2025 by pmocz
6
Procedure arguments with dimension(1) rule A new rule for the linter
#341 opened Mar 2, 2025 by Beliavsky
2
False positives on statement functions bug Something isn't working
#338 opened Feb 28, 2025 by ZedThree
Using "(A)" format to read real or integer data rule A new rule for the linter
#322 opened Feb 11, 2025 by Beliavsky
BitBucket output format enhancement New feature or request
#317 opened Feb 3, 2025 by ZedThree
Suggest standard intrinsic functions when extensions are used rule A new rule for the linter
#303 opened Jan 20, 2025 by Beliavsky
Multiple USE of the same module in the same scope rule A new rule for the linter
#302 opened Jan 16, 2025 by imciner2
Ability to turn off warnings for entire sections of code
#301 opened Jan 16, 2025 by imciner2
1
Add an option to limit the number of errors printed enhancement New feature or request
#294 opened Jan 14, 2025 by Beliavsky
Named constants should be declared and set in the same line rule A new rule for the linter
#292 opened Jan 14, 2025 by Beliavsky
1
Should be able to toggle the summary enhancement New feature or request
#291 opened Jan 14, 2025 by LiamPattinson
Tests should be spread out from fortitude/tests/check.rs
#286 opened Jan 13, 2025 by LiamPattinson
put argument of random_seed should not be a fixed-size array rule A new rule for the linter
#284 opened Jan 13, 2025 by Beliavsky
Suggest that srand and rand be replaced by random_seed and random_number rule A new rule for the linter
#283 opened Jan 13, 2025 by Beliavsky
Suggest that system be replaced by execute_command_line rule A new rule for the linter
#282 opened Jan 13, 2025 by Beliavsky
Only exit or cycle a named do loop rule A new rule for the linter
#280 opened Jan 10, 2025 by Beliavsky
1
Procedures should be separated by blank lines rule A new rule for the linter
#278 opened Jan 10, 2025 by Beliavsky
Indentation of end and else should match beginning of construct or program unit rule A new rule for the linter
#277 opened Jan 10, 2025 by Beliavsky
3
Variable capitalization should be consistent rule A new rule for the linter
#276 opened Jan 10, 2025 by Beliavsky
Support multiple locations/ranges in diagnostics enhancement New feature or request
#271 opened Jan 10, 2025 by ZedThree
ProTip! Type g i on any issue or pull request to go back to the issue listing page.