)]}'
{
  "commit": "4b4ae59599ee17fcf78901aa0cf0bdd31869c1ae",
  "tree": "38979235ca79e0645e2b27d1a60f35634aeb6966",
  "parents": [
    "048d75aa5f881235c88256b6d3fdaaaeadb5aa32"
  ],
  "author": {
    "name": "Travis Cross",
    "email": "tc@traviscross.com",
    "time": "Wed May 14 13:16:27 2025 +0000"
  },
  "committer": {
    "name": "Travis Cross",
    "email": "tc@traviscross.com",
    "time": "Thu May 15 08:01:33 2025 +0000"
  },
  "message": "Fix grammar for `RangePatternBound` regarding literals\n\nThe compiler, in parsing, accepts many more kinds of literals in the\nbound of a range pattern than what we had documented, and as with\n`PatternWithoutRange`, the parser allows each of these literals to be\nprefixed with `-`.  E.g.\n\n```rust\n#[cfg(any())]\nmatch () {\n    ..-true | ..-false \u003d\u003e (),\n    ..-\u0027x\u0027 \u003d\u003e (),\n    ..-b\u0027x\u0027 \u003d\u003e (),\n    ..-\"x\" \u003d\u003e (),\n    ..-r\"x\" \u003d\u003e (),\n    ..-br\"x\" \u003d\u003e (),\n    ..-c\"x\" \u003d\u003e (),\n    ..-cr\"x\" \u003d\u003e (),\n    ..-1 \u003d\u003e (),\n    ..-1.1 \u003d\u003e (),\n}\n```\n\nLet\u0027s fix this by adjusting the `RangePatternBound` production to use\n`LiteralPattern`.  In a separate PR, we\u0027ve adjusted `LiteralPattern`\nto allow for a minus sign ahead of all literal expressions.\n\nTo help the reader, let\u0027s also add a note that highlights that what we\ndiscuss later as being allowed semantically is more restrictive than\nwhat we allow in parsing (and therefore in the grammar).\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2d9ddb5acb3be0a0e509f13c4f097237015f2ea8",
      "old_mode": 33188,
      "old_path": "src/patterns.md",
      "new_id": "d28d58cd93110d83415749591c967205c29a6929",
      "new_mode": 33188,
      "new_path": "src/patterns.md"
    }
  ]
}