wouldn't this be solved by synchronously invalidating everything before computing anything? it seems like that's what the described system is doing tbh, since

wouldn't this be solved by synchronously invalidating everything before computing anything? it seems like that's what the described system is doing tbh, since `setValue` does a depth-first traversal before returning. or is there a gap where that strategy fails you?