Technically the `i is being mutated` at 9:26 is an implementation detail. Kotlin could've implemented for loops over Int ranges as a tail-recursive function and instead of mutating `i`, it would instead call itself but passing a new value of i. Of course, that's inefficient (unless you use the `tailrec` modifier, which will convert it to a loop with mutation anyways)
Indeed, but at this point I’m trying to point out actions when we have them, and for loops are pretty actiony. I suppose more so in C where we have to write our own ;I++
I wish your content didnt use a white background for your IDE. It hurts my eyes to watch it. It if was in dark mode I would watch but sorry I just cant.
Technically the `i is being mutated` at 9:26 is an implementation detail. Kotlin could've implemented for loops over Int ranges as a tail-recursive function and instead of mutating `i`, it would instead call itself but passing a new value of i. Of course, that's inefficient (unless you use the `tailrec` modifier, which will convert it to a loop with mutation anyways)
Indeed, but at this point I’m trying to point out actions when we have them, and for loops are pretty actiony. I suppose more so in C where we have to write our own ;I++
Good stuff! I'm trying to learn more about sequences and this has given a lot to chew on. Love your use of the IDE to make changes quickly and safely.
Thank you, I’m glad it’s useful
I wish your content didnt use a white background for your IDE. It hurts my eyes to watch it. It if was in dark mode I would watch but sorry I just cant.
The problem is that, with old eyes, I can’t see dark mode!
@@PairingWithDuncan Haha all good!
Light theme feels so comfy for me, like reading a book
@razvanfilip3735 Curse you - I’ve literally just started recording this week in dark mode to see how it goes!
@@PairingWithDuncan haha goodluck!