STYLE: Remove unused parameter from SetGlobalInstance and Singleton#4209
Conversation
|
We are probably going to do a major version bump soon, so this might be guarded under future legacy, instead of plain legacy. |
So then, would it still be OK to keep the proposed |
|
Absolutely! |
|
@dzenanz Can you do a Request changes to make it |
|
@dzenanz GitHub automatically made you a co-author of the commits you suggested. Not sure if your co-authorship will be preserved when squashing. 😸 But I would like the commits to be squashed anyway 😄 |
|
Please completely disregard my co-authorship. I prefer a single commit too! |
Added overloads of `SetGlobalInstance` and `Singleton` without the unused `func` parameter. Let the new `SetGlobalInstance` overload just return `void`, instead of `bool`. Deprecated the original overloads, and made them `ITK_FUTURE_LEGACY_REMOVE`. Follow-up to: pull request InsightSoftwareConsortium#4164 commit 6d1c4c7 "STYLE: SingletonIndex does not need to store the unused `func` parameter" pull request InsightSoftwareConsortium#4162 commit 6ec6328 "STYLE: Let `Singleton` assume that SetGlobalInstance always returns true"
f812c52 to
eec0c42
Compare
|
/azp run ITK.Linux.Python |
|
I think the PR is ready now, but the CI says:
Any clue? |
|
I overrode it. |
Added overloads of
SetGlobalInstanceandSingletonwithout the unusedfuncparameter. Let the newSetGlobalInstanceoverload just returnvoid, instead ofbool. Deprecated the original overloads.Follow-up to:
pull request #4164 commit 6d1c4c7
"STYLE: SingletonIndex does not need to store the unused
funcparameter"pull request #4162 commit 6ec6328
"STYLE: Let
Singletonassume that SetGlobalInstance always returns true"