Add explicit move semantics to objects used in std::vector - may improve performance
These objects are using directly in std::vector in trigger code. Adding explicit move semantics should improve performance as they may not be automatically generated otherwise.
Merge request reports
Activity
added Trigger master review-pending-level-1 labels
CI Result SUCCESSAthena AthSimulation externals cmake make required tests optional tests Full details available at NICOS MR-22490-2019-04-08-23-40
Athena: number of compilation errors 0, warnings 0
AthSimulation: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST 36706]added review-approved label and removed review-pending-level-1 label
mentioned in commit 81d0432e
added sweep:ignore label
Please register or sign in to reply