)]}'
{
  "commit": "96917d0541db09977afaba3e6f8a53bfb31bcf45",
  "tree": "72cd32968e3a3749923f6b7a0b42a1e4f5e60d1e",
  "parents": [
    "a1371f3288f2d84cea90a9157ed9a359226969e2"
  ],
  "author": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Mon Aug 12 13:09:02 2024 -0400"
  },
  "committer": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Fri Sep 13 07:38:56 2024 -0400"
  },
  "message": "gdbsupport/intrusive-list: sprinkle noexcept\n\nSome methods of intrusive_list are marked noexcept.  But really,\neverything in that file could be noexcept.  Add it everywhere.\n\nThe only one I had a doubt about is clear_and_dispose: what if the\ndisposer throws?  The boost equivalent [1] is noexcept and requires the\ndisposer not to throw.  The rationale is probably the same as for\ndestructors.  What if the disposer throws for an element in the middle\nof the list?  Do you skip the remaining elements?  Do you swallow the\nexception and keep calling the disposer for the remaining elements?\nIt\u0027s simpler to say no exceptions allowed.\n\n[1] https://www.boost.org/doc/libs/1_79_0/doc/html/boost/intrusive/list.html#idm33710-bb\n\nChange-Id: I402646cb12c6b7906f4bdc2ad85203d8c8cdf2cc\nReviewed-by: Keith Seitz \u003ckeiths@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2262d9fb4270d184a77f01b17c6af2bdb64ec352",
      "old_mode": 33188,
      "old_path": "gdbsupport/intrusive_list.h",
      "new_id": "3c9245fd052f832d9d0de8d3f808882c8b622b11",
      "new_mode": 33188,
      "new_path": "gdbsupport/intrusive_list.h"
    }
  ]
}