-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[math] look at node in proper order #18617
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
base: master
Are you sure you want to change the base?
Conversation
Test Results 21 files 21 suites 3d 6h 34m 47s ⏱️ Results for commit 573a314. ♻️ This comment has been updated with latest results. |
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.
It is probably correct, but can we have a simple test showing the problem existing before?
Also, why the condition is now from <= to < ?
Thanks for the review
To be consistent with the block starting at line 590.
I think I do not know enough of this class to prepare a test, sorry :s |
which uses the FindInRange function
@lmoneta: So, the sorting is more "optimized" after this patch, even if the total number of elements does not change.
![]() |
This Pull request:
Changes or fixes:
This solution copies the same structure from lines 590 where the if-else statements are doing something different.
See
root/math/mathcore/src/TKDTree.cxx
Lines 575 to 581 in 65b3913
Fixes https://its.cern.ch/jira/browse/ROOT-10374
Checklist: