Shay Lewis

@nathanhammond Do you have ideas for what sorts of APIs these sorts of use cases end up wanting, or thoughts on which decisions in the proposal as it stands preclude...

I think we want to first nail down exactly what we want a set inside a computed to do, and then we'll be able to figure out which consequences follow...

@fabiospampinato Yeah, IMO the best possible outcome here would be: - we come up with a semantics for all operations that makes it impossible to observe whether a dependency is...

@mutech: > As far as I can see, all that is needed from signals to make them work with a separate transaction mechanism is an interface allowing a transaction manager...

There are definitely async-related reasons to want these on States, but if there was an async-related reason we needed them on Computeds I'm blanking on that one. (It's possible @modderme123...

@dead-claudia That makes `useSelected` rerun if the map changes but the value at the key in question doesn't, since it performs both reads directly.

Yeah, that's the same idea as where I was going and where Solid tries to go with `createSelector` (although theirs is a slightly different beast is an eager system with...

I wonder if this means `getPending` isn't quite the right primitive to offer. In addition to not working nicely with States, it also has this slightly odd nonlocal behavior where...

We may want to clarify terminology around "dirty" vs. "maybe dirty" -- some systems use both, and I'm not sure what expectations `isDirty` sets from just name alone. (Does it...

Hmm, the most instructive thing is probably something like `mayHaveChanged`, but if we have multiple things referring to dirty or pending statuses in the API it may be worth introducing...