That's very kind of you to say, Derek! I'm so glad you're enjoying it!

Thank you so much, Doug! I'm having lots of fun creating them! 🙂

Thanks Jon! I know that animation in the wrong place or time can be more distracting than helpful, so I'm trying to be intentional about where I put it. I'm glad to hear that it worked well here! 🙂

Yeah, I also wish they were in stdlib. While poking around with things, I did see that the Kotlin compiler itself does make use of the immutable collections library. Sounds like the Kotlin team has lots of big things planned for after the K2 compiler lands, so I'm hoping we'll see this library get closer to a version 1.0 after that. Especially since the prototype code they showed about Collection Literals at the KotlinConf keynote included PersistentSet. 😁

His website (in the video description) is a valuable resource and his "Start Learning Kotlin" illustrated guide is structured like a course 👍

Hey Prosper, thanks so much! I'm actively working on a course, but it's still very early. I'd be happy to set you up with "super-early" access if you're interested. If you're on LinkedIn or Twitter, just send me a direct message (or you can email me... dave at typealias), and I'll get you set up.

Wow, thank you so much - I'm really glad you enjoyed it! More videos are in the works! 🙂

Thanks so much, Abhimanyu! Are you looking for content about how to _use_ a particular DSL, or about how to make your own DSLs?

@@typealias As an Android dev, Gradle groovy was very complicated for me to understand. Hoping to understand Kotlin DSL better as there is a shift from Groovy to Kotlin as the recommendation now from Google. From basics, to advanced levels possible.

Ah, gotcha - thanks! Yes, the Gradle DSL is definitely easier to use with Kotlin Gradle Script than with Groovy, but there's is still quite a learning curve. I've got some research I'll need to do for that one! I'll get add it to the topic list.

Thanks so much Jason! Glad you liked it! 🙂

Thanks so much Mike! I'm glad you like them!

Thank you so much, Sarath!

You're most welcome! I'm glad you liked it! 👍

Yeah, and in most apps, performance is not as important as good structure and readability, anyway. At least in this case, I'd say we get both better performance _and_ better readability with buildList than with list concatenation. In any case, it'd be interesting to see some benchmarks on different Kotlin targets (JVM, Android, native, JS, WASM, etc.), for different sizes of lists to get a better understanding.

@@typealias Yes, I won't dispute the improved readability at all!

Ah, thanks for pointing that out - I didn't realize there's an issue using them with Compose MP. I'll take a look when I get a chance!

Haha, yeah! It's one of those things that, the more I used it, the more I realized I needed it. 🙂

Haha, "Dave Leeds" -> "Dev Lead" 😅 I see what you did there!

Haha, definitely will do! 😁

Hi Ava - As used here, there are no functional differences between those two approaches. The return types are different, though - mapIndexedTo() returns the list, whereas forEachIndexed() returns Unit. So, in situations where you might want to chain calls together, mapIndexedTo() might be a more natural fit. But since we aren't chaining calls in these examples, forEachIndexed() is a fine choice!

@@typealias Got it. Thanks. I wonder why your IntelliJ didn't show a warning at that contents.mapIndexedTo line that the returned value is ignored. Mine sometimes does. Also notice that jdk 15 was used in this video. Was this video recorded 2.5 years ago?

For videos, I often set the inspection level to "Syntax", to minimize distractions. In this case, though, even with the inspection level set to "All Problems", I'm still not getting a warning. Maybe there's a particular inspection that isn't enabled here...? About the JDK - you're very observant! This was recorded more like 2.5 _weeks_ ago. I do actually have more recent JDK versions here, so I'll use those in future videos. 🙂