Understanding Ownership in Rust

곡유
μ†ŒμŠ€ μ½”λ“œ
  • κ²Œμ‹œμΌ 2024. 04. 24.
  • 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
  • κ³Όν•™κΈ°μˆ 

λŒ“κΈ€ • 287

  • @letsgetrusty
    @letsgetrusty  2 λ…„ μ „ +15

    πŸ“Get your *FREE Rust Cheatsheet* : www.letsgetrusty.com/cheatsheet

  • @enderger5308
    @enderger5308 3 λ…„ μ „ +375

    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
      @letsgetrusty  3 λ…„ μ „ +143

      You are one of the chosen.

    • @ddastoor
      @ddastoor 3 λ…„ μ „ +18

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

    • @inx1819
      @inx1819 3 λ…„ μ „ +52

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

    • @comradedownpressor1218
      @comradedownpressor1218 2 λ…„ μ „ +4

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

    • @OggerFN
      @OggerFN 2 λ…„ μ „ +5

      @@ddastoor
      because it's about the same problem

  • @eileennoonan771
    @eileennoonan771 4 κ°œμ›” μ „ +21

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

  • @tullochgorum6323
    @tullochgorum6323 2 λ…„ μ „ +94

    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.

  • @nathanielwoodbury2692
    @nathanielwoodbury2692 3 λ…„ μ „ +212

    You're an incredible teacher, so much clarity.

    • @islapthebass
      @islapthebass 2 λ…„ μ „ +9

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

    • @carloslfu
      @carloslfu 2 λ…„ μ „ +4

      +1

    • @kayakMike1000
      @kayakMike1000 λ…„ μ „ +2

      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
      @-karter-4556 8 κ°œμ›” μ „ +3

      Basically just summarizing the book

    • @playfulyogi5639
      @playfulyogi5639 8 κ°œμ›” μ „ +2

      @@-karter-4556 almost word for word plagiarism

  • @desrucca
    @desrucca 2 λ…„ μ „ +22

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

  • @Haitaish
    @Haitaish λ…„ μ „ +2

    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!

  • @SKyrim190
    @SKyrim190 2 λ…„ μ „ +6

    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

  • @jesusmtz29
    @jesusmtz29 λ…„ μ „ +9

    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

  • @giovannimazzocco499
    @giovannimazzocco499 2 λ…„ μ „ +19

    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!

  • @scheimong
    @scheimong 2 λ…„ μ „ +3

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

  • @kmaximoff
    @kmaximoff κ°œμ›” μ „

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

  • @bobbybob628
    @bobbybob628 2 λ…„ μ „ +1

    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
    @martynclarke8400 λ…„ μ „ +1

    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
    @agustindeluca2304 2 λ…„ μ „ +10

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

  • @biocuts
    @biocuts 2 λ…„ μ „

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

  • @andythedishwasher1117
    @andythedishwasher1117 λ…„ μ „ +15

    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
      @kellyrankin8844 λ…„ μ „ +1

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

  • @aaronkingcto
    @aaronkingcto λ…„ μ „ +9

    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
      @kayakMike1000 λ…„ μ „

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

  • @yichizhang5707
    @yichizhang5707 2 λ…„ μ „ +2

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

  • @twentyeightO1
    @twentyeightO1 λ…„ μ „ +1

    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.

  • @eslamelsharkawy9660
    @eslamelsharkawy9660 λ…„ μ „

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

  • @Antonio-ix3fw
    @Antonio-ix3fw λ…„ μ „

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

  • @sukarnarut
    @sukarnarut λ…„ μ „

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

  • @bigtymer4862
    @bigtymer4862 2 λ…„ μ „ +1

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

  • @almuaz
    @almuaz 5 κ°œμ›” μ „ +1

    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 :)

  • @MCGreen13
    @MCGreen13 λ…„ μ „

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

  • @TheOriginalJohnDoe
    @TheOriginalJohnDoe 2 λ…„ μ „ +1

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

  • @TheKisem
    @TheKisem 10 κ°œμ›” μ „

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

  • @michaeljburt
    @michaeljburt 18 일 μ „

    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.

  • @ViniciusKrolow
    @ViniciusKrolow λ…„ μ „

    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 πŸ‡§πŸ‡·

  • @abdullahfurkanozbek7558
    @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.

  • @TheSkepticSkwerl
    @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.

  • @Souljacker7
    @Souljacker7 λ…„ μ „

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

  • @ostap418
    @ostap418 2 λ…„ μ „

    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

  • @exoticcoder5365
    @exoticcoder5365 3 λ…„ μ „ +1

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

  • @rishkum536
    @rishkum536 2 λ…„ μ „

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

  • @samdavepollard
    @samdavepollard λ…„ μ „ +4

    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.

  • @garotalibertaria7219
    @garotalibertaria7219 10 κ°œμ›” μ „

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

  • @adamtak3128
    @adamtak3128 2 λ…„ μ „ +4

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

  • @Tobi-gl2lb
    @Tobi-gl2lb λ…„ μ „

    Thanks a lot for this series. Very good explained.

  • @WarrenMarshallBiz
    @WarrenMarshallBiz λ…„ μ „

    This channel is pure gold, thanks man!

  • @opticonor
    @opticonor λ…„ μ „

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

  • @rusty9060
    @rusty9060 2 λ…„ μ „ +1

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

  • @user-qr4jf4tv2x
    @user-qr4jf4tv2x 9 κ°œμ›” μ „

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

  • @muthuisheree
    @muthuisheree λ…„ μ „

    Thank you for the wonderful explanation. Extremely valuable

  • @AndrewLighten
    @AndrewLighten κ°œμ›” μ „

    Brilliant explanation. Thank you.

  • @alfredomenezes8814
    @alfredomenezes8814 λ…„ μ „

    This lesson was amazing, thank you very much πŸ¦€β€οΈ

  • @nikhilsinha2191
    @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

  • @-karter-4556
    @-karter-4556 8 κ°œμ›” μ „ +1

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

  • @dixztube
    @dixztube 8 κ°œμ›” μ „

    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

  • @sahilverma4077
    @sahilverma4077 3 λ…„ μ „ +3

    awsome explanation, keep up the good work

  • @avisalon4730
    @avisalon4730 λ…„ μ „

    Thanks! Very understandable video. Easy to learn.

  • @sundaymanali5854
    @sundaymanali5854 2 λ…„ μ „ +1

    10:53 gold info here. love this channel

  • @tahsinulhaqueabir1046
    @tahsinulhaqueabir1046 λ…„ μ „

    Best video on rust ownership

  • @finkelkop7204
    @finkelkop7204 λ…„ μ „

    Realy good explanation. TY!

  • @user-bu3hz5be5w
    @user-bu3hz5be5w λ…„ μ „

    Thanks! Very good explanation!

  • @glebirovich4519
    @glebirovich4519 3 λ…„ μ „ +3

    Hey mate! Keep going! Very well explained.

  • @MultiKB13
    @MultiKB13 2 λ…„ μ „ +1

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

  • @MrPflanzmann
    @MrPflanzmann 2 λ…„ μ „

    I love this videos. Great work!

  • @teenspirit1
    @teenspirit1 λ…„ μ „ +2

    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
      @fennecfox2366 8 κ°œμ›” μ „

      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
      @fennecfox2366 8 κ°œμ›” μ „

      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.

  • @srinivasvalekar9904
    @srinivasvalekar9904 2 λ…„ μ „ +3

    *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

  • @connorzittrauer3306
    @connorzittrauer3306 λ…„ μ „

    This video was great. Thank you πŸ‘

  • @MrSerler
    @MrSerler λ…„ μ „

    thank you so much. great tutorial.

  • @ronny332
    @ronny332 3 κ°œμ›” μ „

    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.

  • @hieverybody4246
    @hieverybody4246 8 μ‹œκ°„ μ „

    This is by far the toughest part of Rust. I really wish the book had a ton more examples and explained things far better.

  • @marlonou8818
    @marlonou8818 2 λ…„ μ „

    Save me time reading thru the chapter myself πŸ˜„

  • @hamzadlm6625
    @hamzadlm6625 λ…„ μ „

    I love u, thanks for the clear explanation

  • @_pro_grammer_
    @_pro_grammer_ 3 κ°œμ›” μ „

    finally learning rust πŸ’™

  • @fennecfox2366
    @fennecfox2366 8 κ°œμ›” μ „

    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.

  • @rizaldi4563
    @rizaldi4563 2 λ…„ μ „ +1

    Omg! Thankyou so much!!!

  • @foobar1269
    @foobar1269 2 λ…„ μ „

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

  • @asjn3e
    @asjn3e 2 λ…„ μ „

    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

  • @LuisMateoAriasCaicedo
    @LuisMateoAriasCaicedo κ°œμ›” μ „

    Thank you very much!

  • @workflowinmind
    @workflowinmind 2 λ…„ μ „

    I needed this! Thanks

  • @sentimentalbaboon4262
    @sentimentalbaboon4262 2 λ…„ μ „

    Great video, thank you!

  • @aleksandrbakhmach9810
    @aleksandrbakhmach9810 λ…„ μ „

    Awesome, thanks man!

  • @Ludwig_Van_Aristossine
    @Ludwig_Van_Aristossine 2 λ…„ μ „

    FINALLY SOMEONE WHO DO STUFF IN CODE INSTEAD OF TALKING IN AIR :D

  • @googleuser2016
    @googleuser2016 2 λ…„ μ „

    Great tutorial!

  • @uovo
    @uovo λ…„ μ „

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

  • @bitfluent
    @bitfluent λ…„ μ „

    Idk who invented the borrowing/ownership concept, but it's genius.

  • @_jirkaa_5170
    @_jirkaa_5170 λ…„ μ „

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

  • @ChrisHalden007
    @ChrisHalden007 λ…„ μ „

    Great video. Thanks

  • @quangle5701
    @quangle5701 2 λ…„ μ „

    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

  • @codelearner4449
    @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.

  • @hansrudolf5849
    @hansrudolf5849 λ…„ μ „

    Great job!

  • @okarakoo
    @okarakoo 2 λ…„ μ „ +13

    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
      @letsgetrusty  2 λ…„ μ „ +17

      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
      @kodedrhema2288 2 λ…„ μ „

      Ah.. i asked the same question... good reply.. πŸ‘

  • @ksnyou
    @ksnyou 3 λ…„ μ „ +1

    good explanation

  • @_jdfx
    @_jdfx 2 λ…„ μ „

    Still a great video! thank you!

  • @jesusmtz29
    @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?

  • @GlobalYoung7
    @GlobalYoung7 2 λ…„ μ „

    Thank you. πŸ˜€πŸ₯³

  • @TC-nl1vq
    @TC-nl1vq 2 λ…„ μ „ +2

    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.

  • @davidjdoherty
    @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?

  • @zb2747
    @zb2747 2 λ…„ μ „

    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!

  • @JavierGonzalez-rc5kx
    @JavierGonzalez-rc5kx 2 λ…„ μ „

    Great video!

  • @snk-js
    @snk-js 2 λ…„ μ „

    wonderful!

  • @bzzzvzzze
    @bzzzvzzze λ…„ μ „

    great video!

  • @ddastoor
    @ddastoor 3 λ…„ μ „ +1

    great video buddy.

  • @sheikhakbar2067
    @sheikhakbar2067 3 λ…„ μ „ +3

    Thanks a lot.

  • @HarshRajput-jr7qp
    @HarshRajput-jr7qp 11 κ°œμ›” μ „

    great video bro

  • @cryptomando
    @cryptomando 2 λ…„ μ „

    Great video