-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
MINOR: [R] Remove whitespace after operator"" #45756
base: main
Are you sure you want to change the base?
Conversation
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename the pull request title in the following format?
or
See also: |
This looks fine, but I'm surprised that it's not giving the warning when compiling on clang20 (https://github.com/ursacomputing/crossbow/actions/runs/13801015462/job/38603309193 for last night). I'll approve + merge this, but curious if you know why this isn't being warned? |
Beats me, I only did a regex GH search to find this. Maybe it only complains about declarations, not |
NVM, I do see it in the logs, it's just not erroring (?):
(searched the logs you shared for (NVM again, I don't see any |
nods yeah, and it doesn't bubble up in https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-clang/arrow-00check.html either. Like I said, I think it's not problematic to merge this regardless, but odd that it's not flagging |
I asked the LLMs and they are just BSing (as anticipated), though Claude happens on the right answer at least https://claude.ai/share/138e5823-cdc8-471d-bd09-c43759396027 |
Rationale for this change
The space after "" is deprecated since it creates ambiguity with reserved _-initial names per:
https://en.cppreference.com/w/cpp/language/user_literal
What changes are included in this PR?
Whitespace change:
Are these changes tested?
No
Are there any user-facing changes?
No