Hello 🙂 I really like your videos - they are informative and touch subjects I do not know much about, and you have a pleasant voice to listen to. Thank you for taking your time to educate people!
I'd love to see you do a video on diving deeper into Kotlin coroutines and exploring various advanced concepts - your teaching style would surely make it easy to understand.Your Kotlin tutorials are incredibly clear and helpful, making learning the language a breeze!
Thanks, Abhijeet! Great suggestion! I'm currently working on the final chapter of the Illustrated Guide, which covers the essentials of coroutines. As I'm doing that, I expect I'll create some videos that either tie in with it, or which cover related concepts that go beyond the essentials. 👍
1:26 As of 1.5 Kotlin has the option to generate lambdas using invokedynamic instead of classes, in 2.0 this behavior will be activated per default. You forgot to mention that inline functions also allow reified generics! But overall, very nice explanation. I will reference your video to others in need. Keep it up 🫡
Thanks for mentioning this! I hadn't read the 2.0-RC1 release notes yet, so I'm glad to hear that this will become the default behavior in 2.0! Also - the omission of reified type parameters was quite intentional - that's a big enough topic for its own video, so we'll tackle that another time. 🙂 Thanks again!
Hey Martinus, thank you so much! The funds from each purchase of the book have gone back into tooling and services that help me to create more articles and videos - so I really appreciate it!
Hey Eslam - The save() function was hiding inside the code folding (if you look at the numbers on the left-hand side, you'll see they go from 1 to 9, because I folded lines 1-8). The implementation of the save() function was irrelevant to the main focus of the video, but in case you're wondering, it just does Thread.sleep() for a random amount of time between 0-500ms.
I tried to use noinline parameter but when I saw the bytecode I found both of parameters inline and noinline both of them dont' make a new object why if there is one of them is noinline
When you compile an inline function, you'll notice it show up in the bytecode (or in Java that you got when decompiling that bytecode) for interoperability with Java. If you call an inline function from Java, it'll call this function - that call won't be inlined, but it'll still work. That function is not called from your Kotlin code, though - it's only there for Java interop. For the Kotlin side, you'll see different bytecode depending on your version of Kotlin - - In Kotlin 1.x, you'll see something like (Function0)null.INSTANCE to represent the noinline argument. - In Kotlin 2.x, your noinline argument is generated as a static function (e.g., private static final Unit main$lambda$2()), and your call site will reference that.
![Kotlin. Inline Functions. Inline Classes [Ru, Kotlin] / Мобильный разработчик](/img/1.gif)
Best kotlin channel
Great examples! The table at the end summed everything up very nicely!
The best explanation I've seen on this topic!
Hello 🙂
I really like your videos - they are informative and touch subjects I do not know much about, and you have a pleasant voice to listen to. Thank you for taking your time to educate people!
Hey Emilio, you're most welcome! And thank you - I truly enjoy creating these videos!
I'd love to see you do a video on diving deeper into Kotlin coroutines and exploring various advanced concepts - your teaching style would surely make it easy to understand.Your Kotlin tutorials are incredibly clear and helpful, making learning the language a breeze!
Thanks, Abhijeet! Great suggestion! I'm currently working on the final chapter of the Illustrated Guide, which covers the essentials of coroutines. As I'm doing that, I expect I'll create some videos that either tie in with it, or which cover related concepts that go beyond the essentials. 👍
Thanks, video is really helpful and good examples along the way to demonstrate actual usage!
This guy is amazing, explains everything so clearly
Thanks so much, Alan!
Thank God I discovered this channel. You rock!
Hey, thanks so much! I'm glad you're enjoying it!
Finally, it was a great explanation. Majority of sophisticated computer science topics are essential once somebody explains it to you.
1:26 As of 1.5 Kotlin has the option to generate lambdas using invokedynamic instead of classes, in 2.0 this behavior will be activated per default.
You forgot to mention that inline functions also allow reified generics!
But overall, very nice explanation. I will reference your video to others in need. Keep it up 🫡
Thanks for mentioning this! I hadn't read the 2.0-RC1 release notes yet, so I'm glad to hear that this will become the default behavior in 2.0!
Also - the omission of reified type parameters was quite intentional - that's a big enough topic for its own video, so we'll tackle that another time. 🙂
Thanks again!
Perfect explanation, thank you :)
You're most welcome!
great video as always!
So beautifully explained. Thanks a lot
Hello, I just bought your book, I think your explanation is very easy to understand.
Hey Martinus, thank you so much! The funds from each purchase of the book have gone back into tooling and services that help me to create more articles and videos - so I really appreciate it!
Thanks for the great explanation. could you please also explained reified key word
Great suggestion! I'll add that to the list of possible future topics. 👍
thanks for explain every things easily but I have a question where function save came form ?
Hey Eslam - The save() function was hiding inside the code folding (if you look at the numbers on the left-hand side, you'll see they go from 1 to 9, because I folded lines 1-8). The implementation of the save() function was irrelevant to the main focus of the video, but in case you're wondering, it just does Thread.sleep() for a random amount of time between 0-500ms.
@@typealias thanks 🙏
Finally, i understood this concept, thank you so much!
I think default inline is just a suggestion to the compiler and cannot be enforced
I tried to use noinline parameter but when I saw the bytecode I found both of parameters inline and noinline both of them dont' make a new object why if there is one of them is noinline
When you compile an inline function, you'll notice it show up in the bytecode (or in Java that you got when decompiling that bytecode) for interoperability with Java. If you call an inline function from Java, it'll call this function - that call won't be inlined, but it'll still work. That function is not called from your Kotlin code, though - it's only there for Java interop.
For the Kotlin side, you'll see different bytecode depending on your version of Kotlin -
- In Kotlin 1.x, you'll see something like (Function0)null.INSTANCE to represent the noinline argument.
- In Kotlin 2.x, your noinline argument is generated as a static function (e.g., private static final Unit main$lambda$2()), and your call site will reference that.
Thanks that's great