3 ms·
Ah, fair. I've never actually seen that become a problem, but I can see how it would be if I were doing more extensive Java interop.
by lolinder 6y ago
Ah, fair. I've never actually seen that become a problem, but I can see how it would be if I were doing more extensive Java interop.
- lmm 6y agoYeah, if all your code and libraries are Kotlin then there's less risk of a collection being mutated under you (though even then, Kotlin gives you no way to write a method that only accepts an immutable collection - you can write a method that accepts a view-only interface, but it will always be possible to pass a mutable collection and mutate it in parallel while that method is running). But of course in that scenario there's also zero benefit from having compatibility with the Java collections.