)]}'
{
  "commit": "0bb15457dec3cd95bb0fbbb74f7d71690dec60d6",
  "tree": "58673b050aa6861a1c12f0d1cd8426a7ea3c6d8b",
  "parents": [
    "a18e6d9d1473d9b25581dd04bef6c7577999631c",
    "d14491567baac1fb3303000d3b6a824f38b06183"
  ],
  "author": {
    "name": "Matthias Krüger",
    "email": "476013+matthiaskrgr@users.noreply.github.com",
    "time": "Sat Jan 24 15:35:08 2026 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sat Jan 24 15:35:08 2026 +0100"
  },
  "message": "Rollup merge of #149174 - GrigorenkoPV:const_block_item, r\u003dme,ytmimi\n\n`const` blocks as a `mod` item\n\nTracking issue: rust-lang/rust#149226\n\nThis adds support for writing `const { ... }` as an item in a module. In the current implementation, this is a unique AST item that gets lowered to `const _: () \u003d const { ... };` in HIR.\n\nrustfmt support included.\n\nTODO:\n- `pub const { ... }` does not make sense (see rust-lang/rust#147136). Reject it. Should this be rejected by the parser or smth?\n- Improve diagnostics (preferably they should not mention the fake `_` ident).\n",
  "tree_diff": []
}