)]}'
{
  "commit": "6ef80e147c63ad84cd616cb4d664b1caf0dbc4bf",
  "tree": "efd1d69cd17af75684ba80c30a1123e57d8f6dfb",
  "parents": [
    "3860147a7f36ea89bc5a19ce229bfd686432c01b"
  ],
  "author": {
    "name": "Nick Kreeger",
    "email": "nick.kreeger@microsoft.com",
    "time": "Thu Jan 15 16:26:12 2026 -0600"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Jan 15 17:26:12 2026 -0500"
  },
  "message": "[mlir][AsmParser] Fix comment detection in string literals (#174125)\n\nThe error positioning logic in emitWrongTokenError() would incorrectly\nidentify \u0027//\u0027 inside string literals as comment starts when backing up\nto position diagnostics. For example, a URL like \"http://example.com\"\nwould cause the error to point at the \u0027://\u0027 instead of the end of the\nline.\n\nAdd findCommentStart() helper that properly skips \u0027//\u0027 occurrences\ninside string literals by tracking quote state and handling escape\nsequences.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0efe30727a2ea052eca48394cc93b73753c3b446",
      "old_mode": 33188,
      "old_path": "mlir/lib/AsmParser/Parser.cpp",
      "new_id": "22928df03fbc72eaf68ca281bd0fc194f7d66727",
      "new_mode": 33188,
      "new_path": "mlir/lib/AsmParser/Parser.cpp"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "9d3a5983bc3ea9c2640ecff29e91fbb17c6efda2",
      "new_mode": 33188,
      "new_path": "mlir/test/IR/parser-string-literal-comment.mlir"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "c78d92c6355e7c28c243d181fbebccabab8ff437",
      "new_mode": 33188,
      "new_path": "mlir/test/IR/parser-string-literal-url.mlir"
    }
  ]
}