Understanding Ownership in Rust

The ultimate Rust lang tutorial. Follow along as we go through the Rust lang book chapter by chapter.
📝 Get your FREE Rust Cheatsheet: www.letsgetrusty.com/cheatsheet
The Rust book: doc.rust-lang.org/stable/book/​
Stack & Heap explanation: • Pointers and dynamic m...
0:00 Intro
0:40 Ownership Model
4:30 Stack & Heap
6:53 Ownership Rules
7:21 Variable Scope
8:22 Memory & Allocation
10:32 Ownership & Functions
12:23 References & Borrowing
18:34 The Slice Type
24:56 Outro
#letsgetrusty​ #rust​lang #tutorial

[@letsgetrusty]

📝Get your *FREE Rust Cheatsheet* : www.letsgetrusty.com/cheatsheet

[@enderger5308]

I don’t know why, but the borrow checker doesn’t confuse me that much. Use a reference when you want to see the original memory through a window, move when you want the data for yourself, and never have a window to a place that does not exist.

[@letsgetrusty]

You are one of the chosen.

[@ddastoor]

a good example from soft engg is to compare the ownership model with read-write lock semantics...

[@inx1819]

The basics of borrow checking isn't hard, but sometimes it can get tricky and very confusing in complicated code

[@comradedownpressor1218]

This is the best concise explanation of borrowing I've seen yet

[@OggerFN]

@@ddastoor because it's about the same problem

[@tullochgorum6323]

As a line-of-business developer I've been a bit intimidated about learning an innovative system language like Rust - but this makes one of the gnarliest features seem learnable. You're a good teacher.

[@stardustbiscuits]

Wait until u learn traits

[@tonybelonog2941]

@@stardustbiscuits so crazy true

[@nathanielwoodbury2692]

You're an incredible teacher, so much clarity.

[@islapthebass]

He doesn't derail ever, seamless additive commentary, and an enjoyable voice haha

[@carloslfu]

+1

[@kayakMike1000]

Most of what he said about stacks and heaps was misleading enough that I don't think he really understands it very well.

[@-karter-4556]

Basically just summarizing the book

[@playfulyogi5639]

@@-karter-4556 almost word for word plagiarism

[@eileennoonan771]

I am going to watch this every day until I understand it in my bones

[@king_james_official]

REAL

[@desrucca]

Finally, found someone that covers the rust guide book. Thanks, man. Super time saver

[@letsgetrusty]

Glad I could help!

[@SKyrim190]

I think that was the best explanation I've come across so far...you took the time a noobie would need to learn this stuff, and didn't try to "keep under two minutes" destroying the clarity for the sake of speed. Also, you didn't jump immediately to metaphors of "oh, its like if you have a book, and you lend it to someone, but that person can write on the book" and so on...I also find those unnecessary and confusing sometimes

[@giovannimazzocco499]

This is by far the best explanation about Rust's borrow mechanism I've encountered so far! The course is an excellent resource for Rust newcomers. Great work!

[@jesusmtz29]

im amazed at how much the rust-analyzer and compiler are teaching me without even running code. You're explanation makes it a top-grade experience

[@brennancurrier806]

Video form of the book helps me so much, I read really slow, you covered the entire chapter in 25 min shorter than I could probably read it lol.

[@scheimong]

Wish I had this video last year when I was learning Rust. You explained the concepts fantastically.

[@Haitaish]

10:53 "When we pass in parameters into a function its the same as if we were to assign s into another variable" - now that's when the borrow checker finally clicked for me. Now I also understand why it's so controversial to some people. Your tutorial so clear and easy to understand. Thank you!

[@bobbybob628]

The very best channel for Rust learners that I have found so far! Thank you, buddy! Wish you all the best and prosperity to your channel!

[@martynclarke8400]

Honestly man, your videos have really helped me whilst I go through the book. Theres a lot of information to consume so appreciate you taking the time to make these accompanying videos (y), some things are easier to see than to read and vice versa :)

[@agustindeluca2304]

Mindblowing 🤯🤯🤯 Thank you so much for your dedication. You're an incredible teacher!

[@biocuts]

You explained it in a very concise and clear way. Good job!

[@yichizhang5707]

I read the rust book ownership chapter but was confused. Your video makes the concept much clearer. Thanks and keep it up!

[@eslamelsharkawy9660]

I think this is the best video on KZbin to explain the ownership model. Great Work.

[@aaronkingcto]

This is really fantastic! Your cadence, examples and explanations are really great! I've been programming for 25 years (C++, C#, Js, etc etc) and this is a really nice way to understand nuances of rust. Thank you!

[@kayakMike1000]

25 years and this rank amateur explains things well? What? Are you one of those php script monkeys? It was awful.

[@exoticcoder5365]

good work ! I understand a lot ! can't wait to see more Rust content !

[@Antonio-ix3fw]

I have just started learning Rust and your videos are helping me to understand all the tricky Rust concepts. Thanks! .

[@samdavepollard]

Very nice series As a hobbyist who's dabbled in a bunch of languages because it's fun, i'm now learning me some rust. Certainly doing my share of fighting with the borrow checker but that said, i'm super impressed with the errors and warnings that the compiler spits out. Most helpful messages that i've encountered in any language; have helped me sort out a bunch of things which in other languages i would have had to fire up the google to work out what was going on.

[@kmaximoff]

I was worried learning Rust, but more I look at this. THIS MAKES SO MUCH SENSE!

[@andythedishwasher1117]

So I recently just made my first foray into Rust by attempting to build a calculator in a Yew app. I am still struggling with the logic itself, but I actually found the battle with the borrow checker to be one of the more refreshing sorts of problems I ran into. It made me think so much harder about where I was declaring my variables and where I was mutating them that it kinda just felt like my brain was steadily increasing in mass and wrinkle count the whole time.

[@kellyrankin8844]

this is how I sort of interpreted it.."stop doing these things unless you really need to because they're just problematic"

[@TheKisem]

First tutorial series on KZbin where I don't even hesitate for a second before clicking the thumbs up button. Great job!

[@TheSkepticSkwerl]

i took an online course, it was short but still, it explained Strings and string slices. (literals) etc... but the way you explained them in this video were so much more clear. thank you.

[@abdullahfurkanozbek7558]

Perfect explanation, even though the concept is hard to understand, the explanations and examples provided in this video are very valuable. Thank you for it.

[@almuaz]

I read the book and i was overwhelmed of new terms and information. this video helped me to visualize it live. yes rust book visualizations were great but for me i find this more helpful. i think after watching this, i will understand the book better. thank you. there are too little learning resources for rust :)

[@ostapsulyk]

Thank you so much, I am learning rust after java and javascript background, and it's quit tough. But your videos help a lot! Thank you

[@sukarnarut]

Awesome teaching. The pace is very good and information goes straight into my brain with good understanding of the concept.

what a great explanation I was so confused now that I decided to learn the language and you made it all clear for me in 25min YOU ROCKS! thx from 🇧🇷

[@bigtymer4862]

Going through the rust book right now... very helpful!

[@TheOriginalJohnDoe]

You sir... are an incredible teacher and have just got a new subscriber!

[@rishkum536]

Beautiful video bro. Thanks for creating this. I understand what is so special about Rust now

[@opticonor]

Great vid, looking forward to watching the rest of them!

[@dixztube]

I work with node and go for my serious business projects but I did get a offer from a firm that uses rust and pretty flexible timeline if I ever wanted to onboard. This got me into going through the rust book and learning the language… I really like it! I also liked go a lot too.. probably because I started in insane crazy js land now these relatively new languages seem to nice

[@MCGreen13]

This was the best outline of this topic that I’ve seen. Thank you.

[@Souljacker7]

I was struggling understanding Steve Klabnik's and Carol Nichols' book, but you made it perfectly clear. Thanks!

[@michaeljburt]

Right around 14:10 was the lightbulb moment for me. And being a long time C and C++ programmer I think I'm finally starting to see why this Rust thing makes sense... What a clever way to make sure that we know who is writing data and who is just reading or calling getters. It makes the C/C++ way of using references, pointers and const seem kind of silly.

[@adamtak3128]

Really good video. I'll be coming back to this over and over until it's stuck in my memory.

[@nowarm]

Thank you for making this. It's so helpful and so easy to follow along. You're amazing

[@Tobi-gl2lb]

Thanks a lot for this series. Very good explained.

[@garotalibertaria7219]

Best explanation about ownership and borrowing, it helped me a lot.

[@WarrenMarshallBiz]

This channel is pure gold, thanks man!

[@twentyeightO1]

Man I'm getting all worked up converting my c++ program to rust. 2 days in and I am no where near to finish it. Now I've realized that my "c++ way of thinking" is getting in the way.

[@nikhilsinha2191]

I have watched tilll 17:19 and can say the explanation is top notch took me 45 min to react this point as I am coding as well the information which I find useful will continue from here the next day

[@alfredomenezes8814]

This lesson was amazing, thank you very much 🦀❤️

[@-karter-4556]

I wish I found this language sooner 😫. The control and defined, predictable behavior is so appealing.

[@user-qr4jf4tv2x]

the reference and borrow is definingly the best part of this tutorial

[@sahilverma4077]

awsome explanation, keep up the good work

[@muthuisheree]

Thank you for the wonderful explanation. Extremely valuable

[@teenspirit1]

7:57 - why would you have to use new to allocate memory on the heap in C++? Just use std::string s("hello"), or std::vector and it works just like it did since 30 something years, memory is deallocated at the end of scope.

[@fennecfox2366]

True, you don't have to manage the memory yourself with raii data structures. Be aware these data structures are still doing dynamic allocation, but they are doing it in a safe way. You still take a potential performance hit but memory leaks shouldn't be an issue.

[@fennecfox2366]

You can use a std::array if you want to avoid the free store and use automatic(commonly referred to as stack) storage. Std::array requires a size known at compile time.

[@glebirovich4519]

Hey mate! Keep going! Very well explained.

[@letsgetrusty]

Thanks Gleb!

[@avisalon4730]

Thanks! Very understandable video. Easy to learn.

[@fennecfox2366]

Coming from c++ this is intuitive. Unique pointers and move semantics give this type of behavior as options in modern c++ so having them as the default makes sense. Also having the const as default on refs is another good safety measure. I do think a basic understanding of pointers in c and references and smart pointers in c++ will help people understandownership and the ideas it's built upon.

[@MrPflanzmann]

I love this videos. Great work!

[@rusty9060]

17:16 is such an elegant info. I love how they designed Rust language

[@finkelkop7204]

Realy good explanation. TY!

[@AndrewLighten]

Brilliant explanation. Thank you.

[@sundaymanali5854]

10:53 gold info here. love this channel

[@MultiKB13]

This video is incredible, I can’t believe you don’t have more subs

[@connorzittrauer3306]

This video was great. Thank you 👍

[@workflowinmind]

I needed this! Thanks

[@rizaldi4563]

Omg! Thankyou so much!!!

[@user-bu3hz5be5w]

Thanks! Very good explanation!

[@MrSerler]

thank you so much. great tutorial.

[@AdamZMouchnic]

I have a question. The shared_ptr template has been in C++ since 2003. Why do people still claim that objects are freed manually using delete?

[@fennecfox2366]

Yes, the modern c++ idiom is to avoid raw pointers and use raii and smart pointers for any object needing ownership. It's probably because they are communicating to people who don't know the difference between c and c++ so explaining those differences takes a backseat to categorizing the languages broadly. I agree with your point.

[@ronny332]

What I really like about your videos, until now :-), is the speed, you tell things. I'm not native American or English, but most every tutorial I watched for instance on Udemy was so slow. Of cause someone can speedup the video, but sometimes, the speaker speaks faster or changes slides, and that results in confusion. Very, very well done, again until here 🙂as I don't know more of your videos besides the seen ones.

[@_jirkaa_5170]

When I watched 2 hour tutorial for rust and was completly confused but now its like really easy

[@googleuser2016]

Great tutorial!

[@sentimentalbaboon4262]

Great video, thank you!

[@codelearner4449]

You're an amazing teacher thanks man. The way you expained how rust stops two mutable references in the same scope to prevent race conditions. If I am not wrong, this feature isnt there in golang, and this is where rust outshines. This feature will outshine even more, when concurrency comes into play. Explaining why rust promotes safe concurrency. Correct me if I got this right.

[@hamzadlm6625]

I love u, thanks for the clear explanation

[@ChrisHalden007]

Great video. Thanks

[@hansrudolf5849]

Great job!

[@asjn3e]

for my new job i have to learn rust fast and i'm not really good at reading documentations and books so thank you for great and useful videos

[@Asgallu]

Great video!

[@LuisMateoAriasCaicedo]

Thank you very much!

[@GlobalYoung7]

Thank you. 😀🥳

[@foobar1269]

Thank you for explaining stack and heap. Now Rust makes more sense in terms of making some of the code design pattern decisions.

[@aleksandrbakhmach9810]

Awesome, thanks man!

[@marlonou8818]

Save me time reading thru the chapter myself 😄

[@bzzzvzzze]

great video!

[@_pro_grammer_]

finally learning rust 💙

[@_jdfx]

Still a great video! thank you!

[@srinivasvalekar9904]

*Me* : Casually starts to watch video to understand closures After sometime , Can't stop watching other videos. I was so deeply involved in listening your videos, I noticed a background music, could you please tell me which song it is :D

[@quangle5701]

Thanks for the video. I would like to know how to apply the slice and ownership for the array of String objects (not &str), especially when passing them to a function as arguments ? Thanks

[@okarakoo]

Thanks for the video. I have a question about the code example in the "Stack & Heap" section: - Is there any reason why a() and b() are defined within main() scope rather than, more commonly, outside main()? - a() is actually never called by main() and therefore neither is b(). Do the stack frames get constructed anyway as in the picture?

[@letsgetrusty]

No particular reason for a() and b() being defined inside main(). Stack frames will not be created unless the functions are called so my example code isn't 100% accurate. Good eye!

[@kodedrhema2288]

Ah.. i asked the same question... good reply.. 👍

[@HarshRajput-jr7qp]

great video bro

[@a.paudel1301]

I love you, This is awesome.

[@ddastoor]

great video buddy.

[@snk-js]

wonderful!

[@ksnyou]

good explanation

[@cryptomando]

Great video

[@hanshaun1350]

This is BY FAR the hardest part to learn Rust. It's frustrating to learn without any C background tbh.

[@kqvanity]

I genuinely don't understand that claim. I might get that you'd 'appreciate it more' not having to deal with either garbage collection/erroneous manual memory management, but not having C/C++ being a prerequisite to learn rust

[@jesusmtz29]

Great video. I've been trying to watch more than a couple of times and read the book to fully understand why some types are made a copy of by default and some get's ownership transfered? What was the feature in mind?

[@uovo]

You are a machine gun of free and high quality knowledge wow

[@davidjdoherty]

Great video. Helped clarify things for me on how this works. Do you guidance on programming styles you recommend when it comes to moving/copying/etc? E.g. when to implement methods as references vs. copies, etc. Side note, the return of the first word function was s.len(), not i. Wouldn't the correct implementation of that return i?

[@TC-nl1vq]

Great video series! I really like your videos. One question though - I know it might seem a bit picky. During your stack & heap explanation you say, for method b() the value of var x gets stored in the heap. However it is not a "mut" - wouldn't this apply to mutable variables only or is it based on the type (string in this case)? Thanks in advance and keep going.

[@saxenaarpit10]

It is based on the type.

[@tahsinulhaqueabir1046]

Best video on rust ownership