After implementing #14, I've been wondering if that could cause memory issues. I can think of some memory leaks caused by deliberate behavior, but I also think that in most cases it should not cause user-perceivable problems.

Still, I don't like that approach, saving the value on each link makes me feel insecure. Finally I discovered that we can have a
push-pull-push model solution that doesn't use version/value at all.

The new push-pull-push model is very similar to the approach adopted by vuejs/core#5912.

• First push: signal/computed pushes dirty/toCheckDirty flag to subscribers
• Second pull: computed/effect pull updates from toCheckDirty dependencies when executed
• Final push: When computed is pulled, if the value is updated, pushes dirty flag to shallow subscribers

In this method, we don't need to use intermediate variables to detect changes, because all flag updates are immediate as needed.

Memory Usage improvement

Since Link does not need to store value, the memory usage is reduced by 3% (2434.72KB -> 2363.90KB) in the following test.

const start = process.memoryUsage().heapUsed;

const w = 100;
const h = 100;
const src = signal(1);

for (let i = 0; i < w; i++) {
	let last = src;
	for (let j = 0; j < h; j++) {
		const prev = last;
		last = computed(() => prev.get() + 1);
	}
	effect(() => last.get());
}

src.set(src.get() + 1);

console.log(`Memory Usage: ${((process.memoryUsage().heapUsed - start) / 1024).toFixed(2)} KB`);

Benchmark Results

main bench

This PR