)]}'
{
  "commit": "4bb05dc562c0d5f32436bf31d75d3f96f4677601",
  "tree": "bd627167d92d5024c659c95f99e329b813edd1ef",
  "parents": [
    "51616a6dfe4d75b7078fa06857a2ccc719a43e7b"
  ],
  "author": {
    "name": "Ömer Ağacan",
    "email": "omersa@google.com",
    "time": "Fri Apr 04 04:04:24 2025 -0700"
  },
  "committer": {
    "name": "Commit Queue",
    "email": "dart-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri Apr 04 04:04:24 2025 -0700"
  },
  "message": "[dart2wasm] Don\u0027t dartify JS values when returning as void\n\nWhen calling a JS function that returns `void`, avoid dartifying the\nresult.\n\nTechnically the return value of `void` functions can still be used, by\ncasting the return type to `Object?` or `dynamic`. However this\nshouldn\u0027t be done, and `dartifyRaw` overhead just to support this case\nwhich should be extremely rare is too much.\n\nAny hacky code that uses return values of `void`-returning JS interop\nfunctions can manually dartify the retrun values with `toDart` or\nsimilar.\n\nIssue: https://github.com/dart-lang/sdk/issues/60357\nChange-Id: Ic370c7cf6eb6982f61f8a07c91e3bb93c5345ac6\nReviewed-on: https://dart-review.googlesource.com/c/sdk/+/417240\nReviewed-by: Srujan Gaddam \u003csrujzs@google.com\u003e\nReviewed-by: Martin Kustermann \u003ckustermann@google.com\u003e\nCommit-Queue: Ömer Ağacan \u003comersa@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "796ae7b95af898f9063b1b52b159ec41b3710968",
      "old_mode": 33188,
      "old_path": "pkg/dart2wasm/lib/js/util.dart",
      "new_id": "82cc9dc051d84c2206c1d8d691ac673ea5ff8e8b",
      "new_mode": 33188,
      "new_path": "pkg/dart2wasm/lib/js/util.dart"
    }
  ]
}