07:53
<annevk>
yulia | sick: littledan: I could make the Module Loading call tonight if that's helpful, please lmk
14:48
<littledan>
A lot of people seem to be out today; I think we should try to convene in two weeks for the module call
16:02
<Mathieu Hofman>
Since we're talking about this stuff, reminder that https://github.com/tc39/proposal-faster-promise-adoption exists
Yes I need to get back to that proposal. I have on my list of tasks to rewrite a user land promise implementation that side-steps some other issues we've found with promises (e.g. memory leaks), and has the ability to get insight into the adoption of unresolved promises. I'm hoping that could help me find ways to rewrite the promise steps in a way that is both mostly compatible with existing behavior, but also enshrines some beneficial behavior that is currently left out by most implementations, such as detection of cycles longer than 2 promises, or these extra ticks incurred by adoption.
21:10
<Justin Ridgewell>
I think we could pretty easily expose the is-not-a-proxy-and-doesn't-have-an-own-.then with that proposal (but we'd be getting further away from faster promise adoption core)
21:10
<Justin Ridgewell>
At least, we could refactor the check in a way that it can be exposed later.