Skip to content
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

Update developer_guide.md with new guidance on quoted internal includes #15238

Merged

Conversation

harrism
Copy link
Member

@harrism harrism commented Mar 5, 2024

Description

Follow up to #15063 to add new guidance for quoting includes of internal headers from src paths. Also covers clang-format include grouping.

Also fixes a single include that was added with <> recently that should be "". #15063 updated all includes to match the guidance in this PR (changing a lot of <> to "" for includes from src/....

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@harrism harrism added doc Documentation non-breaking Non-breaking change labels Mar 5, 2024
@harrism harrism self-assigned this Mar 5, 2024
@harrism harrism requested a review from a team as a code owner March 5, 2024 23:48
@harrism harrism requested review from davidwendt and nvdbaranec March 5, 2024 23:48
@github-actions github-actions bot added the libcudf Affects libcudf (C++/CUDA) code. label Mar 5, 2024
* We use clang-format for grouping and sorting headers automatically. See the
`cudf/cpp/.clang-format` file for specifics.
* Use `<>` for all includes except for internal headers that are not in the `include/cudf`
directory. In other words, if it is a cuDF internal header (e.g. in the `src` or `test`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this apply to cudf_test? That means we will need to change all test files to use #include "cudf_test/...".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, because cudf_test is a library with public headers in include/cudf_test. Therefore includes of its public headers should use <>. Moreover, there is a separate regex grouping for cudf_test in .clang-format.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added clarification of this (and nvtext) in the guide.

@harrism
Copy link
Member Author

harrism commented Mar 6, 2024

/merge

@rapids-bot rapids-bot bot merged commit b5bc531 into rapidsai:branch-24.04 Mar 6, 2024
73 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Documentation libcudf Affects libcudf (C++/CUDA) code. non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants