-
Notifications
You must be signed in to change notification settings - Fork 118
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.
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
Improved style of m_ComputePerThreadVariable data members #132
Open
N-Dekker
wants to merge
7
commits into
main
Choose a base branch
from
STYLE-ComputePerThreadVariables
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
N-Dekker
commented
Mar 29, 2019
Still need to fix this error, before merging:
|
N-Dekker
force-pushed
the
STYLE-ComputePerThreadVariables
branch
2 times, most recently
from
March 31, 2019 22:08
d089c1e
to
9e6ca5a
Compare
Made data members of `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` private, including their `m_ComputePerThreadVariables` member.
Declared m_ComputePerThreadVariables of both as `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` as an `std::vector<AlignedComputePerThreadStruct>`, instead of a raw pointer to the structs. Simplified zero-initialization of the structs. Removed manual `delete[]` statements. This commit aims to improve modern C++ style, and avoid memory leaks.
Removed the `mutable` keyword from `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` data members. The `mutable` keyword should only be used when really necessary (specifically for const-correctness).
this is actually a candidate class that can be moved to the new ITK5 threading mechanism, at it is quite stand alone. Could you have a stab Niels? |
Made data members of `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` private, including their `m_ComputePerThreadVariables` member.
Declared m_ComputePerThreadVariables of both as `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` as an `std::vector<AlignedComputePerThreadStruct>`, instead of a raw pointer to the structs. Simplified zero-initialization of the structs. Removed manual `delete[]` statements. This commit aims to improve modern C++ style, and avoid memory leaks.
Removed the `mutable` keyword from `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` data members. The `mutable` keyword should only be used when really necessary (specifically for const-correctness).
Just did git rebase develop, git pull, git push, hoping to fix the compile errors. |
…SuperElastix/elastix into STYLE-ComputePerThreadVariables
N-Dekker
added a commit
that referenced
this pull request
May 5, 2022
Made data members of `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` private, including their `m_ComputePerThreadVariables` member. Based on the first commit of pull request #132 "Improved style of m_ComputePerThreadVariable data members". Follows C++ Core Guidelines (April 10, 2022): "C.133: Avoid protected data" http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rh-protected
N-Dekker
added a commit
that referenced
this pull request
May 5, 2022
Made data members of `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` private, including their `m_ComputePerThreadVariables` member. Based on the first commit of pull request #132 "Improved style of m_ComputePerThreadVariable data members". Follows C++ Core Guidelines (April 10, 2022): "C.133: Avoid protected data" http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rh-protected
N-Dekker
added a commit
that referenced
this pull request
May 5, 2022
Declared m_ComputePerThreadVariables of both as `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` as an `std::vector<AlignedComputePerThreadStruct>`, instead of a raw pointer to the structs. Simplified zero-initialization of the structs. Removed manual `delete[]` statements. Based on the second commit of pull request #132 "Improved style of m_ComputePerThreadVariable data members". Follows C++ Core Guidelines (April 10, 2022): "Avoid calling new and delete explicitly" http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rr-ptr
N-Dekker
added a commit
that referenced
this pull request
May 5, 2022
Declared m_ComputePerThreadVariables of both as `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` as an `std::vector<AlignedComputePerThreadStruct>`, instead of a raw pointer to the structs. Simplified zero-initialization of the structs. Removed manual `delete[]` statements. Based on the second commit of pull request #132 "Improved style of m_ComputePerThreadVariable data members". Follows C++ Core Guidelines (April 10, 2022): "Avoid calling new and delete explicitly" http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rr-ptr
N-Dekker
added a commit
that referenced
this pull request
May 6, 2022
Declared m_ComputePerThreadVariables of both as `AdvancedImageMomentsCalculator` and `ComputeDisplacementDistribution` as an `std::vector<AlignedComputePerThreadStruct>`, instead of a raw pointer to the structs. Simplified zero-initialization of the structs. Removed manual `delete[]` statements. Based on the second commit of pull request #132 "Improved style of m_ComputePerThreadVariable data members". Follows C++ Core Guidelines (April 10, 2022): "Avoid calling new and delete explicitly" http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rr-ptr
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.
No description provided.