Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Refactor haversine_distance to a header-only API #477
Refactor haversine_distance to a header-only API #477
Changes from 1 commit
314580d
0736356
5830b66
4c16cd6
7580661
073e2d7
e37d61e
9d8e3eb
7f2bbad
2448677
0d954e0
7d100dc
daa82a8
c4ba1f7
454d967
a5dab4a
08dfe95
e373065
3ae133e
f8947eb
564cc4c
4a6976e
c208144
21db279
be1226c
8134f12
42f909e
e5cb703
0b78d87
17569c6
d5ef3b7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The top level API seems to have asserted that A and B coordinates must have the same type. The transform iterator generated from these two arrays should have the same type as well?
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.
I'm not sure I follow your question. Can you elaborate?
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.
There's not necessarily a transform iterator. And we do assert that they have the same type. See the implementation file, where it has
It uses
T
as the type template parameter of thelocation_2d<T>
in the assertion, which means that all the underlying data and the radius must have the same type. There's another assertion that the types are floating-point.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.
Thanks, I think I understand this a bit better now. We don't enforce that the iterator on coordinate A to be the same type as coordinate B. As long as they are all iterating on
location_2d<T>
type, and that they are both RAI on device. A concrete example would be that one iterator constructed from adevice_vector<location_2d>
and the other iterator constructed from a pair of cudf columns, it would still suffice this API.