)]}'
{
  "commit": "5647eb4dbab5d28fac36ef97f194bb33e961f31f",
  "tree": "d8bc72f677d5ffef59496ca7fe1170c0b88776a5",
  "parents": [
    "dec7f7d6578e87cbad1fcc436646fb7834126d9e"
  ],
  "author": {
    "name": "Ingvar Stepanyan",
    "email": "me@rreverser.com",
    "time": "Tue Sep 12 00:26:48 2023"
  },
  "committer": {
    "name": "Ingvar Stepanyan",
    "email": "me@rreverser.com",
    "time": "Tue Sep 12 00:26:48 2023"
  },
  "message": "Don\u0027t mark proxy async funcs as Asyncify\n\nIn #19093 both async functions and functions marked with `NAME__async: true` were marked as functions to be processed by Asyncify.\n\nHowever, looking at usages, standalone async functions are currently used with emscripten_proxy_finish-based callbacks and not with Asyncify.\n\nBesides, such functions can\u0027t work with Asyncify unless we add automatic `Asyncify.handleAsync` wrapping around each such function as well. We could do that, but given that there are already is some confusion around what async means for any particular function, it seems better to keep explicit calls to `emscripten_proxy_finish` and `Asyncify.handleAsync` correspondingly.\n\nHence, in this PR I\u0027m not adding more automatic wrapping but instead just removing the assumption for standalone async functions which should somewhat reduce code size as they will no longer be Asyncify-ed when not necessary.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c54968baa31a436a1b8d0747f2a35691337d671e",
      "old_mode": 33188,
      "old_path": "src/jsifier.js",
      "new_id": "42366dd4ebee6200765a2ee32a4d6d3b151ff227",
      "new_mode": 33188,
      "new_path": "src/jsifier.js"
    }
  ]
}