)]}'
{
  "commit": "effcc70c7c901a51bcc0a8d1323f43cd59614870",
  "tree": "f29fdf8320d0ec5a084fe0463a815a7c0fcd255d",
  "parents": [
    "d400f172227fae379377ee30eb2704ab0b39491a",
    "10d29ee606c80356ea2885b63c6996e26fe48d2c"
  ],
  "author": {
    "name": "Ralf Jung",
    "email": "post@ralfj.de",
    "time": "Sat Mar 28 13:15:53 2026 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sat Mar 28 13:15:53 2026 +0100"
  },
  "message": "Rollup merge of #154450 - Zalathar:assert-incr-state, r\u003dfmease\n\nUse the normal arg-parsing machinery for `-Zassert-incr-state`\n\nThe flag parser for `-Zassert-incr-state` currently extracts an `Option\u003cString\u003e`, and then performs an ad-hoc parsing step slightly later. From looking at https://github.com/rust-lang/rust/pull/90386, I can\u0027t see any reason why it doesn\u0027t just use the normal flag-parsing machinery.\n\nA second commit also extracts the underlying implementation to a separate helper function, so that it isn\u0027t cluttering up the main control flow.\n\nI found this while working on larger cleanups to incremental-file loading.\n",
  "tree_diff": []
}