)]}'
{
  "commit": "70da80445174199818dc442ff429bf14bce85bee",
  "tree": "03402183c44427c7a028e62e6eefea3f3d66cfd8",
  "parents": [
    "f433c13b48d80cff4c7f19044557827594ef5eac",
    "882ae150e93f7c1aef17018a64540fa8b5bec943"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Fri Feb 27 14:05:38 2026 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Feb 27 14:05:38 2026 +0100"
  },
  "message": "Rollup merge of #153159 - Zalathar:emit-workaround, r\u003dnnethercote\n\nWork around a false `err.emit();` type error in rust-analyzer\n\nFor whatever reason, rust-analyzer doesn\u0027t see that these calls to `err.emit();` are diverging, so the trailing semicolon makes r-a complain about a type mismatch between `()` and some other type.\n\nRemoving the trailing semicolon makes no functional difference (because the emit still unwinds the stack), but seems to be enough to allow rust-analyzer to see that emitting an error returns `!` in these cases, which silences the false error.\n",
  "tree_diff": []
}