)]}'
{
  "commit": "5b328bcf7e5e56c5cd3c660655348c2d85dea5cf",
  "tree": "7ab5f2e37e57c7d17f36dd75665c1a8c03b0ddb1",
  "parents": [
    "3befb8bdf6a90f6ca5896c532e8618f7f23fddb7"
  ],
  "author": {
    "name": "Eric Huss",
    "email": "eric@huss.org",
    "time": "Tue Aug 18 14:55:47 2026 -0700"
  },
  "committer": {
    "name": "Eric Huss",
    "email": "eric@huss.org",
    "time": "Tue Aug 18 14:55:47 2026 -0700"
  },
  "message": "Fix BLOCK_COMMENT in the context of SHEBANG\n\nThis fixes an issue with the BLOCK_COMMENT grammar as it is used within\nthe SHEBANG rule. The problem is that BLOCK_COMMENT was changed in\nhttps://github.com/rust-lang/reference/pull/2191 so that it relied on\nthe order of how the comments were handled in the COMMENT rule to avoid\nambiguity with OUTER_BLOCK_DOC. However, because SHEBANG is using the\nBLOCK_COMMENT rule directly, we need BLOCK_COMMENT to be able to stand\non its own without relying on the order in COMMENT.\n\nThis fixes an issue with shebang such as:\n\n\t#! /** doc */ [attr]\n\nHere this should be treated as a shebang (because it is a doc block\ncomment).\n\nThe solution is to do the appropriate negative lookahead to exclude\nOUTER_BLOCK_DOC and INNER_BLOCK_DOC.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b5ff203e15fad267b12669cf946ec23d0b59fdb4",
      "old_mode": 33188,
      "old_path": "src/comments.md",
      "new_id": "64b90d8e369e7c40ceb738538a62f125ded9a6c0",
      "new_mode": 33188,
      "new_path": "src/comments.md"
    }
  ]
}