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

opt: properly use Qt containers in range for loops with std::as_const #2145

Conversation

shenlebantongying
Copy link
Collaborator

@shenlebantongying shenlebantongying commented Feb 10, 2025

close #2144

We can probably add a new auto format step to enforce various Clazy auto fixes later. (or not, there should be no barrier on new incoming PRs from new persons.)

The performance impact?

miniscule 😅

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
C Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@shenlebantongying shenlebantongying changed the title opt: properly use Qt containers with STL range for with std::as_const opt: properly use Qt containers in range for loops with std::as_const Feb 10, 2025
@shenlebantongying shenlebantongying merged commit acf58d7 into xiaoyifang:staged Feb 10, 2025
8 of 9 checks passed
@shenlebantongying shenlebantongying deleted the opt/qt-container-range-for-std-as-const branch February 10, 2025 02:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Qt containers in range for is a deep copy when const iterator is not used.
1 participant