[all-commits] [llvm/llvm-project] a40275: [clang] Add explicit std::move(...) to avoid a few...

[serge-sans-paille via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: a40275c8c821c89046111d4954165daba7a24f36
      https://github.com/llvm/llvm-project/commit/a40275c8c821c89046111d4954165daba7a24f36
  Author: serge-sans-paille <sguelton at mozilla.com>
  Date:   2026-02-09 (Mon, 09 Feb 2026)

  Changed paths:
    M clang/lib/Analysis/CloneDetection.cpp
    M clang/lib/Parse/ParseDeclCXX.cpp
    M clang/lib/Sema/SemaTemplateInstantiate.cpp
    M clang/lib/StaticAnalyzer/Core/ProgramState.cpp
    M clang/lib/Tooling/DependencyScanningTool.cpp

  Log Message:
  -----------
  [clang] Add explicit std::move(...) to avoid a few copies (#180482)

Moving an std::vector is almost always profitable.

A clang::CXXScopeSpec contains an owned
clang::NestedNameSpecifierLocBuilder which currently does not benefit
from being moved, but may structurally in the future.

A clang::MultiLevelTemplateArgumentList contains an llvm::SmalVector
which may benefit from being moved dependiong on its size.

A clang::Environment contains an llvm::ImmutableMap which itself
contains an llvm::IntrusiveRefCntPtr that benefits from being moved.

Changes suggested by performance-use-std-move from #179467

---------

Co-authored-by: Timm Baeder <tbaeder at redhat.com>



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications