David Neil

> use `FinalizationRegistry` to clean up those references once those consumers are dropped. I would love to learn more about this, because on paper it seems like holding the strong...

FYI @alxhub I attempted to implement a `FinalizationRegistry` version of Signals, and it breaks down in the following case: ```typescript export const externalState = new Signal.State(1); class Foo { public...

Are you imagining the implementation would check `arguments.length` to differentiate between not passing an argument and passing in `undefined`? I feel like `arguments` access de-optimizes functions, but maybe that would...

So that doesn't let you set the value to `undefined`, though it does let you set the value to `null`

If [AsyncContext](https://github.com/tc39/proposal-async-context) is added to the language, do `Signals` need to do anything to support an `AsyncComputed`, or can it be a user-land construct?