Repository Issue Activity (beta)

#30 Async

#152 Can we use accessor instead of get/set methods?

#282 Why does a Watcher need a 'pending' state?

#281 Provided context vs global, fully pull async computed, my lessons from implementing a fully async signal library

#279 Inconsistency between algorithm and a test

#278 Question: why does this test pass?

#116 Integration Stories

#277 Writable Signal.Computed

#255 Computed signals should expose a callback that is invoked when a value is dropped

#254 Consumers can unexpectedly hold unused memory in dependencies

#271 the discord link at the bottom of the readme is invalid

#275 `Signal` in ECMAScript is bad idea

#273 Retrieving signal values can result in leaky abstractions.

#274 Let's keep things clean and simple: `new Signal(initialValue)`

#272 Consider renaming “Signal” to avoid collision with existing AbortSignal

#263 Intermediate values ​​are ignored, which may not be what we want (immediate effects)

#270 Relation to algebraic effects?

#261 Is it possible to set signal inside `effect` callback?

#148 Why the name "Signal"?

#237 Volatile sources in the computation graph

#265 All internal references within Signals should be weak

#252 Consumers should be held weakly to allow all nodes to be live

#269 Automatic dependency tracking within asynchronous computed functions - proposal to simplify implementations

#124 Getter / Setter pair (prev named Signal.State question)

#243 Add `Signal.Buffer` alongside `Signal.State` and `Signal.Computed`