TC39 Async Context on 2024-04-04

07:56	<Steve Hicks>	Huh, could you elaborate on this? I thought computeds would store their registration context. If you want to traverse the dependency graph to determine causation, there is an introspection API for that A computed signal running in the registration context is problematic. Our UI framework registers the computed signals and effects at app initialization time - so the context would be disconnected from any user-initiated event. Then the event handlers typically set a signal and rely on the signal graph to propagate through to an effect. To add tracing to this, the plan is to start the trace in the event handler, storing it in an async var, and then pick it up in the effect where the UI is eventually updated to finish the trace as completed. If the computeds/effects run in the registration context then there is no way to propagate the trace through this graph (even explicitly, since there's no parameter that can be passed through it like an old-fashioned function-based approach would allow).
11:40	<littledan>	Thanks for the context, Steve. This is really interesting. Would you be interested in joining the signals discord to discuss this further with others in the area? (Or if not, mind if I copy-paste this comment to trigger discussion there?)
11:41	<littledan>	If we wanted AsyncContext to be suitable for something like React Context, then registration time would be really helpful… so I want to think through all sides of this case to understand whether there is a unified answer.
11:45	<Andreu Botella>	Hey, we still haven't added the updates to AsyncContext to the agenda for next week
11:45	<Andreu Botella>	should I open a PR?
13:25	<Andreu Botella>	how much time do we expect the updates to take?
13:28	<Andreu Botella>	Justin Ridgewell:
15:29	<Justin Ridgewell>	Yes please.
15:29	<Justin Ridgewell>	Maybe 15 min if we don’t discus calling context at all?
15:32	<Andreu Botella>	that sounds good
15:33	<Andreu Botella>	Justin Ridgewell: Since I'm opening the PR, I'll add constraints as well. You were unavailable on the 8th, right?
15:33	<Justin Ridgewell>	Yes
15:34	<Andreu Botella>	https://github.com/tc39/agendas/pull/1586
15:35	<Andreu Botella>	whoops, I added it at the end with stage 0 proposals
15:35	<Andreu Botella>	fixed
15:36	<Steve Hicks>	Thanks for the context, Steve. This is really interesting. Would you be interested in joining the signals discord to discuss this further with others in the area? (Or if not, mind if I copy-paste this comment to trigger discussion there?) Sure, I'd be happy to join the discord, but also feel free to copy-paste the comment.