Skip to content

[SYCL] Fix Coverity issues after #16228 #16313

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

Merged
merged 2 commits into from
Dec 10, 2024

Conversation

uditagarwal97
Copy link
Contributor

All of these Coverity issues are related to using std::move() instead of variable copy.

Copy link
Contributor

@maarquitos14 maarquitos14 left a comment

Choose a reason for hiding this comment

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

For cases using push_back(std::move(...)) you can also go for emplace_back(...), so you don't need explicitly std::move. It's just a matter of style though, so up to you.

@uditagarwal97
Copy link
Contributor Author

@intel/llvm-gatekeepers the PR is ready to be merged.

@sarnex sarnex merged commit a1355e8 into intel:sycl Dec 10, 2024
14 checks passed
KornevNikita pushed a commit that referenced this pull request Feb 19, 2025
All of these Coverity issues are related to using `std::move()` instead
of variable copy.
KornevNikita pushed a commit that referenced this pull request Feb 25, 2025
All of these Coverity issues are related to using `std::move()` instead
of variable copy.
KornevNikita pushed a commit that referenced this pull request Feb 25, 2025
All of these Coverity issues are related to using `std::move()` instead
of variable copy.
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.

3 participants