)]}'
{
  "commit": "04591090649e54449ae7ea46dcd1df134be54add",
  "tree": "eea6a5e803d637b92df00a06b25e05ca9f76ed55",
  "parents": [
    "a22e53133b0d7c772257f8c85255e413e3f88ec5",
    "2598e89f8ad7352189cf3434be53a8000f94ee70"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Fri Sep 18 23:05:20 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Sep 18 23:05:20 2026 +0200"
  },
  "message": "Rollup merge of #162946 - nnethercote:simplify-query-stack-printing, r\u003destebank\n\nSimplify query stack printing\n\nCurrently it uses `eprintln!` for the \"query stack during panic\" header and \"end of query stack\" footer and\n`struct_failure_note(..).with_span(..).emit()` for the stack frames. The difference is curious.\n\nLooking more closely:\n- failure notes lack a leading label (e.g. no \"note: \");\n- although the failure note is given a span, the span never renders because the `AnnotateSnippetEmitter` used for the query stack has an empty source map field;\n- the JSON emitter is never involved here.\n\nTherefore, the only difference between using `struct_failure_note` and `eprintln!` is that the former prints in bold. But boldness for frames isn\u0027t important; indeed, normal backtrace frames don\u0027t use bold.\n\nSo the commit changes query stack frame printing to use `eprintln!`, removes some now unnecessary `dcx` arguments, and also removes `struct_failure_note`. That leaves \"For more information about an error, try `rustc --explain {}`\" as the only use of `FailureNote`.\n\nr? @estebank\n",
  "tree_diff": []
}