Fix move semantics in triangulate_poses to improve performance

This commit is contained in:
2026-01-29 17:55:59 +08:00
parent cab98936dd
commit 0ec6a85921

View File

@ -377,7 +377,7 @@ std::vector<std::vector<std::array<float, 4>>> TriangulatorInternal::triangulate
// Triangulate and score // Triangulate and score
auto [pose3d, score] = triangulate_and_score( auto [pose3d, score] = triangulate_and_score(
pose1_core, pose2_core, cam1, cam2, roomparams, core_limbs_idx); pose1_core, pose2_core, cam1, cam2, roomparams, core_limbs_idx);
all_scored_poses[i] = std::move(std::make_pair(pose3d, score)); all_scored_poses[i] = std::make_pair(std::move(pose3d), score);
} }
// Drop low scoring poses // Drop low scoring poses