Auto untracked for self-references

[mlajtos]

From my experience, the untracked/peek is usually used when you want to compute a new value based on previous value, i.e. self-reference. Simple example:

const counter = signal(0)

const increase = () => {
  counter.value = untracked(() => counter.value + 1)
  // or counter.value = counter.peek() + 1
}

Could we get rid of calling untracked/peek for self-references? I think the self-dependency can be easily caught and prevented.

[rschristian]

I'm not sure that's possible with runtime reactivity? Signals boil down to get and set properties, they have no understanding of why they're being used/accessed. For your example, the getter will run first, and then immediately after, the setter will run. There's no context available to the getter to see what it's being assigned to.

Possible I'm being daft and forgetting something, but I believe you'd need a compiler to land what you're suggesting.

---

That being said, I'm struggling to think of a scenario where that's even an issue? An increase function, like you show above, shouldn't be an issue w/ or w/out untracked/peak. I guess you could run into trouble putting counter.value = counter.value + 1 into the body of a component, but you shouldn't do that anyways.