| 21:59 | <shu> | bakkot: ping |
| 22:02 | <bakkot> | shu: pong |
| 22:08 | <shu> | https://docs.google.com/presentation/d/14PNcWgkd3Ik61b0Fv9qFISfjUfGz4ZThCkyC-XTTC_8/edit?usp=sharing for the structured clone slides |
| 22:08 | <shu> | ptal if you have time, and comment with concerns |
| 22:10 | <bakkot> | seems good |
| 22:11 | <bakkot> | I might emphasize that the details of how it works really do not matter, since this is strictly a layering thing for an already existing API |
| 22:11 | <bakkot> | since I guarantee you that e.g. Mark is going to be asking about exactly how it works |
| 22:12 | <shu> | heh yes |
| 22:14 | <shu> | does node have it as well? |
| 22:14 | <shu> | structured cloning, that is |
| 22:16 | <bakkot> | not currently, afaik, but see https://github.com/nodejs/node/issues/39713 |
| 22:17 | <bakkot> | actually, wait, maybe it does via MessageChannel in the worker_threads module |
| 22:18 | <bakkot> | ok yeah: https://nodejs.org/api/worker_threads.html#worker_threads_port_postmessage_value_transferlist
|
| 22:20 | <shu> | excellent, thanks for the reference |
| 22:33 | <bakkot> | mark is going to be so unhappy with this |
| 22:34 | <bakkot> | e.g. if you structured clone a proxy for an array, it throws, thus revealing that you actually had a proxy rather than an array |
| 22:41 | <shu> | the world is already this way, what you gonna do |
| 22:42 | <bakkot> | pretend it isn't |
| 22:42 | <shu> | https://www.youtube.com/watch?v=PwuckTkE7T4 |
| 22:43 | <shu> | well in any case, that's the "we're not asking for normative changes here" |
| 22:43 | <bakkot> | yeah |
| 22:43 | <bakkot> | it's just I suspect mark has maybe not previously heard of or at least though much about this algorithm, so this presentation is going to be how he finds out, and it will make him unhappy |
| 22:44 | <shu> | yeah, seems very likely |