)]}'
{
  "commit": "5c82590d18efcabd4b1efa0afcd7386d4588c121",
  "tree": "1573bb6dcf8c2792cd3dbe63f257a1a54e80afef",
  "parents": [
    "9dfc31d1d9af936c0b62fe252e80dae28828afa9"
  ],
  "author": {
    "name": "Arman Uguray",
    "email": "armansito@google.com",
    "time": "Wed Nov 15 14:20:32 2023 -0800"
  },
  "committer": {
    "name": "Arman Uguray",
    "email": "armansito@google.com",
    "time": "Wed Nov 15 14:51:02 2023 -0800"
  },
  "message": "[encoding] Do not encode zero-length path segments\n\nZero-length segments lead to numerical errors and lead to extra\ncomplexity and wasted work (in the form of thread allocation) for GPU\nflattening. We now detect and drop them at encoding time.\n\nCurrently, a path segment is considered zero-length if all of its\ncontrol points (in local coordinates) are within EPSILON (1e-12) of\neach other. This may not be the desired behavior under transform.\n\nAlso since the length here isn\u0027t in terms of the actual arc length,\nthis won\u0027t detect all curves that are within an EPSILON sized bounding\nbox (which may have a larger distance between their control points).\n\nFor stroking purposes, the distance between the control points is what\nmatters most as that\u0027s what\u0027s used to compute a curve\u0027s tangent.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a4a8905cfc79b7d3a903007b510d138fa02b7995",
      "old_mode": 33188,
      "old_path": "crates/encoding/src/path.rs",
      "new_id": "91bca2c0b8a0626bb3e17880cceac71e4da628a7",
      "new_mode": 33188,
      "new_path": "crates/encoding/src/path.rs"
    }
  ]
}