Kotlin's return value checker - lots of developers missed this one. In this video, I show how you can use it to expect call sites to use the values returned from your functions. See you at KotlinConf this week! youtube.com/watch?v=VDEQh2Jk…

Destructuring has been a popular feature in Kotlin, but since it's been based on position, it comes with some risks. But with Kotlin 2.3.20, you can eliminate many of those risks! Here's what I mean... Since destructuring is based on position, the order of your variables needs to match the order of the components (such as the data class constructor properties). If you accidentally swap around a few of them, you could end up with some surprises, and it's easy to do, especially when several of the components have the same type! But with Kotlin 2.3.20, you can now enable an experimental feature to use name-based destructuring instead! When activated in "complete" mode, the syntax we've been using up until now will match based on name rather than position. This means you can get them out of order, and it still works. If you use a name that doesn't match, you'll get a compiler error. But for those cases where you actually wanted a different name, you can use a new syntax to assign the component to a different name: val (title, cost = price, author) = book Prefer to use the classic, position-based destructuring? You can use brackets instead of parentheses, like this: val [author, cost, title] = book The bracket syntax brings along some connotations of collections, which seems fitting, since position-based destructuring could still be helpful for things like Pair and List. It's still experimental, and there's a full migration path planned out, but you can activate it today with a compiler argument. What do you think about this feature Do you like the new syntax? Have you run into issues with position-based destructuring in the past? #Kotlin #AndroidDev