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

refactor: return-braced-init-list pt 2 of 2 #44870

Merged
merged 2 commits into from
Nov 29, 2024

Conversation

ckerr
Copy link
Member

@ckerr ckerr commented Nov 27, 2024

Description of Change

Finish off the return-braced-init-list changes. Pt 1 was in #44838.

These diffs really are just a lot of return {}; and that's pretty much it 😸

Checklist

Release Notes

Notes: none.

@ckerr ckerr added semver/patch backwards-compatible bug fixes target/32-x-y PR should also be added to the "32-x-y" branch. target/33-x-y PR should also be added to the "33-x-y" branch. target/34-x-y PR should also be added to the "34-x-y" branch. labels Nov 27, 2024
@electron-cation electron-cation bot added the new-pr 🌱 PR opened in the last 24 hours label Nov 27, 2024
@deepak1556
Copy link
Member

Related, any plans to add the clang-tidy checks to the PR lint task to avoid future regressions ?

@electron-cation electron-cation bot removed the new-pr 🌱 PR opened in the last 24 hours label Nov 28, 2024
@ckerr
Copy link
Member Author

ckerr commented Nov 29, 2024

Related, any plans to add the clang-tidy checks to the PR lint task to avoid future regressions ?

It will need to be part off CI, rather than something that runs locally. It's incredibly slow!

One idea that John suggested was to run it on changed cc files in a PR

@ckerr ckerr merged commit f7e823a into main Nov 29, 2024
65 checks passed
@ckerr ckerr deleted the refactor/more-return-braced-init-list branch November 29, 2024 17:44
Copy link

release-clerk bot commented Nov 29, 2024

No Release Notes

@trop
Copy link
Contributor

trop bot commented Nov 29, 2024

I was unable to backport this PR to "32-x-y" cleanly;
you will need to perform this backport manually.

@trop trop bot added needs-manual-bp/32-x-y and removed target/32-x-y PR should also be added to the "32-x-y" branch. labels Nov 29, 2024
@trop
Copy link
Contributor

trop bot commented Nov 29, 2024

I have automatically backported this PR to "33-x-y", please check out #44890

@trop
Copy link
Contributor

trop bot commented Nov 29, 2024

I have automatically backported this PR to "34-x-y", please check out #44891

@trop trop bot added in-flight/33-x-y in-flight/34-x-y merged/33-x-y PR was merged to the "33-x-y" branch. merged/34-x-y PR was merged to the "34-x-y" branch. and removed target/33-x-y PR should also be added to the "33-x-y" branch. target/34-x-y PR should also be added to the "34-x-y" branch. in-flight/33-x-y in-flight/34-x-y labels Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged/33-x-y PR was merged to the "33-x-y" branch. merged/34-x-y PR was merged to the "34-x-y" branch. semver/patch backwards-compatible bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants