-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Consistent ptr typedefs for kd tree flann #1607
Consistent ptr typedefs for kd tree flann #1607
Conversation
|
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.
This should also be modified accordingly.
If that is modified, then this should also be updated, of course. |
Sorry guys, I completely forgot about this! I propose to instantiate only with the default |
That is, to leave it unchanged? My idea was not to instantiate more types. I just wanted to make it clear when reading the instantiations that the class actually depends on two separate types. But if the general acceptance is to leave it like, then this one is good to go. |
I agree that we do not need to preinstantiate with other distance types. So far everyone was happy with the default one. (And which ones would you choose anyway?) As per Sergio's comment, yes, we can update the instantiation macro. But in user code instantiation happens implicitly, so the macro is not really needed. |
Consistent use of 'Dist' template type for users having custom distance functors.