| 18:00 | <Steve Hicks> | I was discussing the Governor proposal with some folks and someone mentioned a question of how it worked with AsyncContext and the async iterator helpers. In particular, my understanding (though I could be wrong) is that there's a slight mismatch between iterator helpers and hypothetical generator-based implementations of those helpers - in particular iter.map() runs the function in the same context that called next() whereas the trivial function* map() would run the mapper in the initial caller's context. I would assume the async iterator helpers will be similar - are these assumptions/understandings correct? |
| 18:10 | <Steve Hicks> | (or are we planning to specify registration-time context for (async) iterator helpers?) |
| 22:55 | <nicolo-ribaudo> | I was discussing the Governor proposal with some folks and someone mentioned a question of how it worked with AsyncContext and the async iterator helpers. In particular, my understanding (though I could be wrong) is that there's a slight mismatch between iterator helpers and hypothetical generator-based implementations of those helpers - in particular iter.map() runs the function in the same context that called next() whereas the trivial function* map() would run the mapper in the initial caller's context. I would assume the async iterator helpers will be similar - are these assumptions/understandings correct? |
| 22:56 | <nicolo-ribaudo> | (and talking with the observables champion, this week we agreed that observables behave consistently with that btw) |