Re:Kotlin 1.0.5 is here
by mike_hearn on Wednesday November 09, 2016 @04:51AM
(#12908692)
Yeah, I was meaning 'for loops' to include the modern sense of foreach loops too. Java doesn't distinguish and Kotlin doesn't have the old style at all.
There's no rule that says a for loop must only support a single iteration interface. That seems more like an implementation detail of the compiler than a problem with for loops in general.
Re:Kotlin 1.0.5 is here
by willtim on Wednesday November 09, 2016 @12:41PM
(#12912525)
Of course the big elephant in the room that I didn't mention, is that for loops get work done via mutation. This is perhaps what was mean't by “unclean".
There's no rule that says a for loop must only support a single iteration interface. That seems more like an implementation detail of the compiler than a problem with for loops in general.