A need for assertWithTimeout()?


I've found a systematic problem in the Javascript implementations of the collection classes. You can read about it here: http://youtrack.jetbrains.com/issue/KT-3035

I wonder if we should add unit tests to detect these problems before we just patch the bugs, but that would require a new assertion. Something like

assertWithTimeout(timeOut, { testCode that might not terminate })

What do you old-timers think of this?

Regards, Tommy


I've reviewed maps.js more and there are no systematic errors, just one error. Sorry for the accusation. :)

There’s now a pull-request that fixes the issue mentioned aboe.

Regards, Tommy