Skip to content
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

Add ITK_DEFAULT_COPY_AND_MOVE and replace "manually" defaulted copy and move member function declarations #4652

Merged

Conversation

N-Dekker
Copy link
Contributor

@N-Dekker N-Dekker commented May 8, 2024

Aims to address issue #4645 "Defaulting copy constructor, copy assignment, move constructor, and move
assignment functions", reported by Jon Haitz Legarreta Gorroño (@jhlegarreta).

@github-actions github-actions bot added area:Core Issues affecting the Core module area:IO Issues affecting the IO module labels May 8, 2024
@dzenanz dzenanz requested a review from jhlegarreta May 8, 2024 17:40
@N-Dekker N-Dekker force-pushed the ITK_DEFAULT_COPY_AND_MOVE branch from 2558ea1 to 0705afe Compare May 8, 2024 20:37
@github-actions github-actions bot added the type:Infrastructure Infrastructure/ecosystem related changes, such as CMake or buildbots label May 8, 2024
@N-Dekker N-Dekker marked this pull request as ready for review May 8, 2024 20:40
@thewtex
Copy link
Member

thewtex commented May 13, 2024

Let's rebase after #4659 to get green CI.

@thewtex thewtex added this to the ITK 5.4.0 milestone May 13, 2024
Explicitly "defaults" the copy constructor, copy assignment operator, move
constructor, and move assignment operator of the specified class.

Addresses issue InsightSoftwareConsortium#4645
"Defaulting copy constructor, copy assignment, move constructor, and move
assignment functions", reported by Jon Haitz Legarreta Gorroño.
Instead of "manually" defaulting their copy and move member functions.

Follow-up to pull request InsightSoftwareConsortium#4639
commit d1ebdfa
"COMP: Fix implicit copy constructor definition deprecation warnings"
by Jon Haitz Legarreta Gorroño
Instead of "manually" defaulting their copy and move member functions.

Follow-up to two commits by Jon Haitz Legarreta Gorroño:

pull request InsightSoftwareConsortium#4626
commit 9aff210
"COMP: Use default copy, move for construc, assign `RealTimeStamp`"

pull request InsightSoftwareConsortium#4627
commit ec2677f
"COMP: Use `default` copy and move construct and assign in `itk::Region`"
@hjmjohnson hjmjohnson merged commit 4f42280 into InsightSoftwareConsortium:master May 15, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:Core Issues affecting the Core module area:IO Issues affecting the IO module type:Infrastructure Infrastructure/ecosystem related changes, such as CMake or buildbots
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants