-
Notifications
You must be signed in to change notification settings - Fork 3.8k
GH-46207: [C++] Rename arrow::util::StringBuilder and move to internal namespace #46813
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
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.
Thanks for tackling the work.
Part of the current problem on CI is with calling the file *_internal.h
. The header file won't be installed and this is used on some of the bindings which requires it. We can move the namespace to arrow::internal
but keep installing the header file, probably naming the files string_util.cc
and string_util.h
?
Thank you for your review. Let me take a look. |
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 for doing this. Just one suggestion, otherwise LGTM.
cpp/src/arrow/util/string_util.h
Outdated
|
||
namespace internal { | ||
namespace detail { |
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 detail
namespace is now superfluous given there's already an enclosing internal
namespace.
340254b
to
9ec056e
Compare
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 for the PR. This looks good to me. @pitrou do you want to take a look? It seems your suggestion has been tackled.
Signed-off-by: Ziy1-Tan <[email protected]>
Signed-off-by: Ziy1-Tan <[email protected]>
@github-actions crossbow submit -g cpp |
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.
+1, thank you for your contribution @Ziy1-Tan . I'll wait for CI to pass and then merge.
Revision: b9c5e4d Submitted crossbow builds: ursacomputing/crossbow @ actions-44ea48c19a |
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 1202d79. There was 1 benchmark result indicating a performance regression:
The full Conbench report has more details. |
@github-actions crossbow submit test-r-rstudio-r-base-4.1-opensuse155 |
Revision: b9c5e4d Submitted crossbow builds: ursacomputing/crossbow @ actions-21818136da
|
) ### Rationale for this change OpenSUSE 15.5 ships old GCC (7.5) that doesn't have enough C++17 support. ### What changes are included in this PR? Use Ubuntu 20.04 that ships GCC 9.3 instead of OpenSUSE 15.5. Ubuntu 20.04 reached EOL but we can use it for now. We discussed why we need OpenSUSE 15.5 based job at #45718 (comment) . We have the job because https://arrow.apache.org/docs/developers/cpp/building.html said "gcc 7.1 and higher should be sufficient". We need require GCC 9 or later with #46813. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: #46989 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
) ### Rationale for this change OpenSUSE 15.5 ships old GCC (7.5) that doesn't have enough C++17 support. ### What changes are included in this PR? Use Ubuntu 20.04 that ships GCC 9.3 instead of OpenSUSE 15.5. Ubuntu 20.04 reached EOL but we can use it for now. We discussed why we need OpenSUSE 15.5 based job at #45718 (comment) . We have the job because https://arrow.apache.org/docs/developers/cpp/building.html said "gcc 7.1 and higher should be sufficient". We need require GCC 9 or later with #46813. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: #46989 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Rationale for this change
arrow::util::StringBuilder
to internal namespace to avoid confusion with classarrow::StringBuilder
What changes are included in this PR?
arrow::util::StringBuilder
toarrow::internal::StringBuilder
arrow::internal::StringBuilder
toarrow::internal::JoinToString
arrow/util/string_builder.{h|cc}
toarrow/util/string_util_internal.{h|cc}
Are these changes tested?
Yes.
Are there any user-facing changes?
No. they are used internally.