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

Codehealth: Run performance-move-const-arg check on the codebase #42230

Closed
cdesouza-chromium opened this issue Nov 12, 2024 · 0 comments · Fixed by brave/brave-core#26497
Closed

Comments

@cdesouza-chromium
Copy link
Contributor

Description

For more details on this check:

https://clang.llvm.org/extra/clang-tidy/checks/performance/move-const-arg.html

@cdesouza-chromium cdesouza-chromium self-assigned this Nov 12, 2024
cdesouza-chromium added a commit to brave/brave-core that referenced this issue Nov 12, 2024
This check has detected a few places where the use of `std::move` has
been completely misleading. In one of them we are potentially incurring
in a bug, as we are moving a shared callback that is being used in a
loop.

https://clang.llvm.org/extra/clang-tidy/checks/performance/move-const-arg.html

Resolves brave/brave-browser#42230
cdesouza-chromium added a commit to brave/brave-core that referenced this issue Nov 12, 2024
This check has detected a few places where the use of `std::move` has
been completely misleading. In one of them we are potentially incurring
in a bug, as we are moving a shared callback that is being used in a
loop.

https://clang.llvm.org/extra/clang-tidy/checks/performance/move-const-arg.html

Resolves brave/brave-browser#42230
@brave-builds brave-builds added this to the 1.75.x - Nightly milestone Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants