| 05:43 | <littledan> | Who is advocating for “in different ways”? |
| 05:45 | <littledan> | Oh I guess you mean, there are different base objects to look it up off of, and signals don’t have any base object at all (unlike the AsyncContext.currentContext API) |
| 05:47 | <littledan> | For Signals: is there any way we could take advantage of the fact that you’re trying to trace something which happens completely synchronously when reconstructing the “what access caused which computeds to be synchronously evaluated” relation (which I take it was the reason for the non-registration-time semantics)? |
| 16:46 | <Steve Hicks> | Yah, "in different ways" is an automatic result of piggybacking off of the Event object - it shifts the question down to the underlying scheduling API, since each such API will necessarily have a different shape and thus a different way to access the causal context. |
| 16:47 | <Steve Hicks> | Many/most/(all?) userland schedulers will be synchronous, so the casual context would generally be the immediately previous one. That said, if one were to double-wrap a callback, then it wouldn't be quite as "immediate" anymore, and I assume we'd like wrap to really be idempotent. |
| 22:09 | <ljharb> | do you want me to cancel yalls meeting next week, since it's plenary week? |
| 22:25 | <littledan> | do you want me to cancel yalls meeting next week, since it's plenary week? |