Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • athena athena
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Jira
    • Jira
  • Merge requests 150
    • Merge requests 150
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Repository
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • atlasatlas
  • athenaathena
  • Merge requests
  • !22482

WIP: Add explicit move semantics to objects used in std::vector - may improve performance

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Adam Edward Barton requested to merge abarton/athena:trigMove into master Apr 08, 2019
  • Overview 3
  • Commits 1
  • Pipelines 0
  • Changes 6

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.

Edited Apr 08, 2019 by Mark Sutton
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: trigMove