Skip to content

C++: remove more upper-case variable names #10435

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Sep 15, 2022
Merged

C++: remove more upper-case variable names #10435

merged 1 commit into from
Sep 15, 2022

Conversation

ginsbach
Copy link
Contributor

This builds on #10420, apologies for not spotting all of these at once!

@ginsbach ginsbach requested a review from a team as a code owner September 15, 2022 13:37
@github-actions github-actions bot added the C++ label Sep 15, 2022
@ginsbach ginsbach added the no-change-note-required This PR does not need a change note label Sep 15, 2022
@jketema jketema changed the title remove more upper-case variable names C++: remove more upper-case variable names Sep 15, 2022
jketema
jketema approved these changes Sep 15, 2022
View reviewed changes
Copy link
Contributor

@jketema jketema left a comment

Choose a reason for hiding this comment

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

As with the other PRs: This looks ok to me. What I do not quite know is whether this might have any impact on things we do not test here (as these are queries of @kind table). I propose we just merge this and see what happens.

@jketema jketema merged commit 8b29235 into main Sep 15, 2022
@jketema jketema deleted the ginsbach/RemoveEvenMoreUpperCaseVariables branch September 15, 2022 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jketema jketema jketema approved these changes

Assignees
No one assigned
Labels
C++ no-change-note-required This PR does not need a change note
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ginsbach @jketema