You would not write this code for a very simple reason: all `setState` calls queue up a new render. Since you're setting the state every time the component is r

You would not write this code for a very simple reason: all `setState` calls queue up a new render. Since you're setting the state every time the component is rendered, it will loop infinitely. Let's say you instead did the `setFoo` and `setBar` in a click handler. In that case, when you click the button it would tell React "Hey, in the next render set `foo = 10` and `bar = 2` (since `foo = 1)`. Then React goes ahead and runs your function again, and `foo` and `bar` will both be updated. The value of `foo` does not change within a render cycle, you literally don't have to worry about state.