-
-
Notifications
You must be signed in to change notification settings - Fork 708
STYLE: Increase code coverage, make intent clear #5562
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
Conversation
The primary purpose for this change is self-serving :). I am using ITK as a talking point in my teaching of how I then noticed that the code coverage exposed code that So I am practicing what I preach to students: Employ So ... my good deed for the day :). |
7d80d9d
to
d270b3b
Compare
Improve code coverage by simplying default code flow paths.
d270b3b
to
782a3d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Improved readability and make the intent of searching for clusters more transparent. As a side effect, the code coverage now is at 100% in the default case where clusters are found.
782a3d9
to
ae049cd
Compare
Improve code coverage by refactoring termination path order.
Improve code intent with explicit variable for determining if a
a cluster is found.
PR Checklist