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
Fix scram b code-checks
warnings associated with FWCore
#31396
Conversation
Mostly this was moving `=delete` methods to public section and removing unnecessary uses of `std::move`.
The code-checks are being triggered in jenkins. |
~LuminosityBlockAuxiliary() {} | ||
LuminosityBlockAuxiliary& operator=(LuminosityBlockAuxiliary&&) = default; | ||
LuminosityBlockAuxiliary& operator=(LuminosityBlockAuxiliary const&) = default; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NOTE: this changed allowed a use of std::move
to actually do something useful.
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31396/18243
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: DataFormats/Provenance @makortel, @smuzaffar, @cmsbuild, @Dr15Jones can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Mostly this was moving
=delete
methods to public section and removing unnecessary uses ofstd::move
.PR validation:
code compiles. Running
scram b code-checks
no longer gives any warning for FWCore/Framework or FWCore/Utilities.