Understanding Ownership in Rust
HTML-код
- Опубликовано: 16 май 2024
- 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 #rustlang #tutorial 
Наука
📝Get your *FREE Rust Cheatsheet* : www.letsgetrusty.com/cheatsheet
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.
You are one of the chosen.
a good example from soft engg is to compare the ownership model with read-write lock semantics...
The basics of borrow checking isn't hard, but sometimes it can get tricky and very confusing in complicated code
This is the best concise explanation of borrowing I've seen yet
@@ddastoor
because it's about the same problem
I am going to watch this every day until I understand it in my bones
REAL
You're an incredible teacher, so much clarity.
He doesn't derail ever, seamless additive commentary, and an enjoyable voice haha
+1
Most of what he said about stacks and heaps was misleading enough that I don't think he really understands it very well.
Basically just summarizing the book
@@-karter-4556 almost word for word plagiarism
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.
Wait until u learn traits
@@stardustbiscuits so crazy true
Finally, found someone that covers the rust guide book. Thanks, man. Super time saver
Glad I could help!
You explained it in a very concise and clear way. Good job!
Wish I had this video last year when I was learning Rust. You explained the concepts fantastically.
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
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!
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!
It was *borrowed* from the book.
Going through the rust book right now... very helpful!
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 :)
I read the rust book ownership chapter but was confused. Your video makes the concept much clearer. Thanks and keep it up!
I have just started learning Rust and your videos are helping me to understand all the tricky Rust concepts. Thanks!
.
This was the best outline of this topic that I’ve seen. Thank you.
Mindblowing 🤯🤯🤯
Thank you so much for your dedication. You're an incredible teacher!
You sir... are an incredible teacher and have just got a new subscriber!
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
I think this is the best video on RUclips to explain the ownership model. Great Work.
Awesome teaching. The pace is very good and information goes straight into my brain with good understanding of the concept.
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.
I was struggling understanding Steve Klabnik's and Carol Nichols' book, but you made it perfectly clear. Thanks!
Beautiful video bro. Thanks for creating this. I understand what is so special about Rust now
Really good video. I'll be coming back to this over and over until it's stuck in my memory.
Best explanation about ownership and borrowing, it helped me a lot.
Thank you for the wonderful explanation. Extremely valuable
Thanks a lot for this series. Very good explained.
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 🇧🇷
the reference and borrow is definingly the best part of this tutorial
good work ! I understand a lot ! can't wait to see more Rust content !
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.
I was worried learning Rust, but more I look at this. THIS MAKES SO MUCH SENSE!
This channel is pure gold, thanks man!
Brilliant explanation. Thank you.
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.
Great vid, looking forward to watching the rest of them!
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
First tutorial series on RUclips where I don't even hesitate for a second before clicking the thumbs up button. Great job!
This lesson was amazing, thank you very much 🦀❤️
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!
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.
this is how I sort of interpreted it.."stop doing these things unless you really need to because they're just problematic"
awsome explanation, keep up the good work
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!
25 years and this rank amateur explains things well? What? Are you one of those php script monkeys? It was awful.
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 :)
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
thank you so much. great tutorial.
Thanks! Very understandable video. Easy to learn.
10:53 gold info here. love this channel
Realy good explanation. TY!
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
17:16 is such an elegant info. I love how they designed Rust language
Thanks! Very good explanation!
This video was great. Thank you 👍
I wish I found this language sooner 😫. The control and defined, predictable behavior is so appealing.
This video is incredible, I can’t believe you don’t have more subs
Hey mate! Keep going! Very well explained.
Thanks Gleb!
I love u, thanks for the clear explanation
I love this videos. Great work!
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.
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
Omg! Thankyou so much!!!
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
Thank you for explaining stack and heap. Now Rust makes more sense in terms of making some of the code design pattern decisions.
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.
Best video on rust ownership
Save me time reading thru the chapter myself 😄
Awesome, thanks man!
finally learning rust 💙
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.
Thank you very much!
You are a machine gun of free and high quality knowledge wow
I needed this! Thanks
Great video, thank you!
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?
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!
Ah.. i asked the same question... good reply.. 👍
Great video. Thanks
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?
Great tutorial!
*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
FINALLY SOMEONE WHO DO STUFF IN CODE INSTEAD OF TALKING IN AIR :D
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?
Great job!
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.
Still a great video! thank you!
good explanation
Thank you. 😀🥳
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.
It is based on the type.
This is BY FAR the hardest part to learn Rust. It's frustrating to learn without any C background tbh.
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
Man thank you - I have to use rust for a project and learning rust through the docs/book along with your video course has helped me a lot! You explain things really well and at a nice talking pace with examples and implementation - thanks bro!
Great video!
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.
Thanks a lot.
Most welcome!
wonderful!
great video buddy.
I read the Rust book a couple of years ago now but never really made use of Rust because all the borrow checking and lower level things made me realize maybe I'm happier staying with C# or some higher level language. I've been wanting to get back into it, or maybe to learn Go. Rust seems quite popular these days so starting to go that way again. Your videos are very well presented, thank you for taking your time to share your knowledge in such a clear and calm way, it's very motivating, much appreciated
If you are already familiar with C#. I would actually recommend you learn a LITTLE bit of C++ before. The Syntax is kinda similar (They are oriented around OOP), but C# has a Garbage Collector, while C++ has only manual memory Management. So you'll learn about pointers, malloc and new, destructors, smart_ptrs, references (to lvalues and rvalues), copy constructor and move semantics.
Those are things, C# does not have. So you can take like a day to learn the Syntax of C++ (How to do in C++ what you can do in C#) and then learn the memory management stuff which is the hard part.
That way you can understand how hard and unreliable this stuff really is, and how rust, using the same abstractions (But with the added concept of borrowing (A type of move) that can be tracked by the borrow checker) can solve the same issues of C++, and a lot more, by default at compile time. And all the weird anoying part of the languages that you struggled with will probably now make sense as a logical next step, or a consequence of the things that you now know are happening under the hood!
You could also just keep going. Rust is s logical simplification of C++. But C++ is just a superset of C created to simplify reasoning about objects instead of just bytes in memory, and as such allowing things like RAII which are imposible in C.
And C is just a logical next step above assembly. Hand compiling C is actually really easy. So you can stick to a subset of C (Just the atomic operations, the one that take a single CPU instructions) and have a very good idea of what's happening under the hood.
@@sebastiangudino9377 yeah thanks, I did learn C and C++ during my Computer Science degree in university years ago, so it's not that I don't know the fundamentals it's more about being familiar or effective in day to day use. What I meant by sticking with high level is because I actually don't want to really think about memory allocation, references etc and just like to work in higher level abstractions :P but ja, Rust started to feel like I needed to know more. So I still want to get into it again, but haven't :)
@@jamesbarrow Yeah! Going low level is just a performance thing. Since other ways there are just expensive allocations and copies EVERYWHERE. But to be fair. If you don't have performance needs you might just not need rust. I personally think Rust is beautifully elegant, but regular old C# can do the job really well
@@sebastiangudino9377 true. I do a lot of web dev, so the traction it's gaining along with Go in the JS tooling communities is making me interested at looking at it again ;)
great video!
@ 17:14 how are r1 and r2 out of scope after line 7 ?
what if I want to use them after the print stmt ?
First of all, thanks a lot for the tutorials! So much easier to learn from your vids than from the actual book.
Now, I wanted to ask (at 17:04), what if I wanted to use r1 or r2 after the println!() statement? How would we approach that?
It will still work as long as you don't use any of them AFTER you declare r3. This is the point where the mutable reference is created and for it to work you must not have any reference (mutable or not) until r3 goes out of scope.
Great video
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.
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.
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.