)]}'
{
  "commit": "a43073a38964b5169c8fd26c5c6fe389ba63d445",
  "tree": "c73936334c37b7e022091c68189c2530c940aa25",
  "parents": [
    "46b4b3b002994ddb9d6fc72268c3e271243cd1df"
  ],
  "author": {
    "name": "Sergey Sharybin",
    "email": "sergey@blender.org",
    "time": "Thu Apr 03 11:47:50 2025 +0200"
  },
  "committer": {
    "name": "Sergey Sharybin",
    "email": "sergey@blender.org",
    "time": "Thu Apr 03 14:23:24 2025 +0200"
  },
  "message": "Fix vector operations benchmark compilation\n\nSome of the benchmark functions use the same name as other functions\nin the ceres namespace. For example Axpby defines both benchmark but\nalso an utility function in eigen_vector_ops.h. It seems to confuse\nsome compilers and leads to a compilation error rooting deeper into\nthe benchmark header itself: it seems that the compiler can not\ndeduct which of the instances of such functions to use.\n\nWrapping the file into an anonymous namespace solves the problem.\nAlternative could be to use benchmark namespace to make thins more\nexplicit, for example ceres::internal::benchmark.\n\nTested on the following configuration:\n- macOS 15.4\n- Xcode 16.3\n- Apple M3 CPU\n- google-benchmark 1.9.2 installed via homebrew\n\nChange-Id: Id127015dd22de99c6c3da88e71f255736e0bed82\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b658ea5c7e145bea95df5f31e806910d955e3407",
      "old_mode": 33188,
      "old_path": "internal/ceres/parallel_vector_operations_benchmark.cc",
      "new_id": "c3dcdb4f7ef68967b0def374e755384b83e09d1b",
      "new_mode": 33188,
      "new_path": "internal/ceres/parallel_vector_operations_benchmark.cc"
    }
  ]
}