-
Notifications
You must be signed in to change notification settings - Fork 27
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
Heavy refactoring suggestion #2
base: master
Are you sure you want to change the base?
Conversation
…hich copied from hongshibao/go-kdtree approach
…kages, ex-points code moved to _test files to let final binary build be lighter, some code formatting for the tests.
Codecov Report
@@ Coverage Diff @@
## master #2 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 5 2 -3
Lines 224 187 -37
=====================================
- Hits 224 187 -37
Continue to review full report at Codecov.
|
Hi @Hiyorimi, Thanks for the pull request. Could you please give some example code specifying your problem? I see that you added |
I used Extra modules, which are used only in tests, are redundant in application aiming to deal with high load, and it is also keeps package more simple. Besides, these point will be anyway overwritten. |
@Hiyorimi I would really like to enable custom distance functions. It would be great to have a good example to be able to test the changes. Do you have one for me? I already have a pretty good implementation draft. |
I didn't change anything nor got back to the project since I submitted PR :) |
Hey! Thank you for a great KDTree implementation. However, I had to alter some code to ease support of KDTrees in my project, so I suggest this refactoring, which you might (or might as well not) find useful.
I had to give up explicit points and range modules, to lessen number of imports. I also removed example classes to the _test files, so they are not imported with the main code.
Thank you for considering this pull request.