We fixed an inconsistency in Kotlin (non-local break & continue)

[@AlanDarkworld]

Non-local breaks and continues are... whatever. I would avoid them in clean code anyways. What I find exciting are the contracts. When will they become stable?

[@cromefire_]

I mean they've been in there for so long, I'd wager they won't change that much anymore anyways. And you also don't need to declare them that often. At least I've just been using them for a while now.

[@kiyo211]

Awesome content (i didn't understand anything)

[@AK-vx4dy]

Felixble but what for extract lambda to tie it again to specific code? I see some use in UI scenarios

[@hashemmousavi2451]

Awesome as always

[@waelluay6902]

What's the name of the theme?

[@TheIsraelMendoza]

It looks like IntelliJ’s default “Dark”.

[@alco8864]

wow, how to color the suspend method @@?

[@EugeneGalonsky]

Settings->Editor->ColorScheme->Kotlin->Functions->Suspend function call

[@Vatk4LI]

thats a great feature

[@donwald3436]

0:00 Bro this isn't tiktok you don't need the ADHD captions lol.

[@MaxWeninger]

Not sure why to write such code that needs this in the first place? Beeing "flexible" does not include writing such weired code :)

[@Salehalanazi-7]

I like allowing this but it feels smelly

[@yalfdev]

Great feature..but Tomato is a real fruit lol

[@sensitive-cod]

onSuccess and onFailure methods are methods that are potentially asynchronous in nature. Thats a bad naming for what you are trying to achieve. Substituting if (result.isFailure) { break } with a result.onFailure { break } is super smelly and, I'd dare to say, dangerous!

[@julio_souza]

You are correct on not liking the number 13, it is also a bad number in Brazil.