bug in Container.updateChildren special cases for a.length == 1 and b.length == 1 with implicit keys

[mraleph]

In both special cases for a.length == 1 here and b.length == 1 here we can perform an update on the last node and exit the loop. At this point i == b.length (or i == a.length depending on the special case in question) because we already incremented i. The code after the loop assumes that this means no update was performed and aNode has to be removed (or bNode should be inserted). Which leads to incorrect DOM update - we either lose DOM node or we get duplicated node.

I can send you a PR if you'd like that fixes the problem.

[localvoid]

Thanks, fixed.

[mraleph]

I upgraded and confirmed that the issue is gone. Awesome, thanks!