-
Notifications
You must be signed in to change notification settings - Fork 208
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
[FEA] Move error.hpp out of detail #1369
Comments
i'd like to take on this once triaged |
@lamarrr go for it, your help is welcome! I have been making related changes lately (part of #1417). Note that step one is to search all of RAPIDS repos for uses of the detail functions and if any exist, then we have to do a first PR like 1417 that removes nothing and adds public API versions of the functions. Then PRs to update the RAPIDS repos that use the detail functions / types to the new public functions / types should be submitted and merged before a final PR that removes the old detail functions / types. This is the only way to avoid breaking downstream builds. |
@harrism there is no detail namespaced type/function in the error.hpp header. so I suppose it should be okay to move them out to a public header and leave the internal macros in the detail folder. |
That's good. There are 5 files across cuDF, cuGraph and RAFT that |
@lamarrr I think you can consider this triaged. If you open your PR after today, you should target |
noted! |
Once merged, I'll refractor the upstream repost to use the public API |
I've moved the public part of error.hpp out of the detail header as described in #1369 Fixes #1369 Authors: - Basit Ayantunde (https://github.com/lamarrr) - Lawrence Mitchell (https://github.com/wence-) - Mark Harris (https://github.com/harrism) Approvers: - Michael Schellenberger Costa (https://github.com/miscco) - Lawrence Mitchell (https://github.com/wence-) - Mark Harris (https://github.com/harrism) URL: #1439
Is your feature request related to a problem? Please describe.
Currently the header error.hpp is in the detail directory. However, it contains user-facing error definitions, which should not be coming from a detail header.
Describe the solution you'd like
The header should be moved out of the detail directory.
Describe alternatives you've considered
None
Additional context
There are some pieces of the header (such as the macros) that may not belong in a publicly visible header. If so, we may need to refactor a bit to avoid exposing those.
The text was updated successfully, but these errors were encountered: