Amazing content, as always! The Kotlin standard library safari is definitely my favourite series on this channel! Also, I did not know before that Kotlin has undefined behaviour (although very limited of course)
It's undefined behaviour due to the algorithms, unlike C or C++ where UB is inherent to (some aspects of) the language. Kotlin the language, being based on the JVM which doesn't have UB, doesn't have UB either.
Now know the difference between .reversed() and .asReversed()! Actually it makes sense, since the "as" part in function names almost almost indicates that you're providing a different view or perspective on an object (in comparison to "to" which always provides a new copy of it)
If [] is translated to calling get(), why can't Kotlin provide get(slice : Pair) and get(slice: Range) polymorph functions to work as the slice function. This way we can write list[1 to 3] instead of list.slice(1 to 3). Of course, we can extend the List.get() ourselves, but I am just wondering why Kotlin does not provide that in its standard library.
Amazing content, as always! The Kotlin standard library safari is definitely my favourite series on this channel! Also, I did not know before that Kotlin has undefined behaviour (although very limited of course)
It's undefined behaviour due to the algorithms, unlike C or C++ where UB is inherent to (some aspects of) the language. Kotlin the language, being based on the JVM which doesn't have UB, doesn't have UB either.
Seen it was a bit since these have been uploaded and just want to say please do more!!! They are super helpful!
Awesome video, thank you for the tips & tricks on the usage of List & MutableList
This is the best educational video I have seen, I like so much kaolin and I thought it was really cool how you explained it in a relaxed way.
Great series well done 👏🏽👏🏽
Now know the difference between .reversed() and .asReversed()!
Actually it makes sense, since the "as" part in function names almost almost indicates that you're providing a different view or perspective on an object (in comparison to "to" which always provides a new copy of it)
Awesome high quality video 👍 Good job a always 🙂
PS: I wonder where the candy 🍬 went. Might come across it in later episodes perhaps? 😁
I always learn a lot by this entertaining videos. Kotlin is so powerful. :)
Thank you so much for this excellent explanations.
Good sharing!
views is something we need to deal carefully. Thanks for sharing awesome content
Well done!
Amazing content! ❤ Jetbrains
today I learned something new about lists which is Views 🤯
If [] is translated to calling get(), why can't Kotlin provide get(slice : Pair) and get(slice: Range) polymorph functions to work as the slice function. This way we can write list[1 to 3] instead of list.slice(1 to 3). Of course, we can extend the List.get() ourselves, but I am just wondering why Kotlin does not provide that in its standard library.
What about search on lists
When calling toList on a List does the function do a Shallow Copy of the List?
Subscribed just now.
I want to learn kotlin right from basics. Help me please
nice
I wonder if Sebastian plays Starcraft2. He looks like he should.
Have a nice Kotlin!
So why kotlin don't have *LinkedList()* like java ???
you are geniuses there =)
Using fruits images instead of characters makes it difficult to read them fast. Not so colorblind friendly.
คุณอ้วนขึ้นนะค่ะ