Deallocate arrays #971
Merged
Deallocate arrays #971
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
Member
hfp
commented
Oct 29, 2025
hfp
commented
- Not actually necessary (modern Fortran).
- Not actually necessary (modern Fortran).
|
yes, allocatable variables are released when they go out of the scope... so why this change is needed? |
|
I had it around for long time and it is now only for consistency like every ALLOCATE get DEALLOCATE. Originally, I wanted to reduce the number of allocated arrays, but code looked to bad when lumping arrays together. What remains (beside of consistency), is deallocation happens likely earlier given automatic cleanup is "at the end of the subroutine". |
|
LGTM. better verbose... |
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.