)]}'
{
  "commit": "45cec8bb3efd627cd4e975335c25619f0e252ccf",
  "tree": "8c8312f2c1fe5d210c5b3df93a4d11cb48ee8ee1",
  "parents": [
    "828e302c7b67abc561e948bdcbcee96bd7561db2",
    "3e0572e7b62a118f845b349f9426d0ca61b7ed68"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Thu Apr 02 22:13:48 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Apr 02 22:13:48 2026 +0200"
  },
  "message": "Rollup merge of #153532 - jdonszelmann:attributes-containing-rustc, r\u003dpetrochenkov\n\nAttributes containing rustc\n\nr? @petrochenkov\n\nI noticed that attributes *containing* the word rustc as a segment also error with a message referring to \"starting with rustc\". The first commit shows this going wrong by re-exporting `#[test]`, a built-in macro, from a module called rustc.\n\nThe 2nd commit addresses this by changing the diagnostic. However, given the wording I wonder if the real solution shouldn\u0027t be to allow attributes containing a `rustc` segment and only disallow them when they start. In other words, actually implement the behavior that the original diagnostic pointed out.\n",
  "tree_diff": []
}