Skip to content

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 25, 2025
All of these Coverity issues are related to using `std::move()` instead
of variable copy.
@uditagarwal97 uditagarwal97 deleted the coverity_2025.1_fix branch November 5, 2025 20:18
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