)]}'
{
  "commit": "baffc5e9bc04e11efe911cf6c56c2792d5cebb4a",
  "tree": "2478b2e426d0a6f627f6b1a35ddde5d64e648cdd",
  "parents": [
    "20612ce8272e09fe158a3b1a2dd18e406d4d1eb9",
    "1fec51c446893ab97a04ba04ea896d29c88e421d"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Mon Mar 23 12:15:01 2026 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Mar 23 12:15:01 2026 +0100"
  },
  "message": "Rollup merge of #154201 - Zalathar:try-set-color, r\u003dnnethercote\n\nUse enums to clarify `DepNodeColorMap` color marking\n\nWhen a function\u0027s documentation has to explain the meaning of nested results and options, then it is often a good candidate for using a custom result enum instead.\n\nThis PR also renames `DepNodeColorMap::try_mark` to `try_set_color`, to make it more distinct from the similarly-named `DepGraph::try_mark_green`.\n\nThe difference is that `try_mark_green` is a higher-level operation that tries to determine whether a node _can_ be marked green, whereas `try_set_color` is a lower-level operation that actually records a colour for the node.\n\nThe updated docs for `try_set_color` also fix a typo: *atomicaly* → *atomically*.\n\nr? nnethercote (or compiler)\n",
  "tree_diff": []
}