Children can't be modified without instantiating new component instances?

[trusktr]

For example, since a component constructor receives children in the second arg, then if children ever change, the only way to have it updated is constructing a new instance? This is unlike React, where the instance is kept alive, and this.props.children is modified. Could this be hint that new instances are being created when maybe there's an alternate way to avoid creating new instances (and thus reduce overhead)?

(same with props if those are only received through constructor)

[zaygraveyard]

As patch.js:52 suggests, the update() method of the component is passed the new props and children as params.