04 Ownership & Borrowing | Rust Tutorials

Check out the entire playlist here: • Rust Tutorials
In this video, I will be covering the stack/heap memory model followed by Rust's Ownership system and borrowing system
Find me elsewhere:
Instagram: / jeff.no.zhao
Github: github.com/kamiyaa

[@laviray5447]

By far the most well explained video on youtube about rust ownership and borrowing. Showing a visual representation of what's happening to the memory was the most important part and it helped me understand everything.

[@zapoyou2]

I’m a few months into learning the programming world, and this is a massive help and explaining these basic concepts to me.

[@SuperPatQC]

Thanks bud, that was the clearest explanation ive seen so far of the borrowing checker !

[@aaryan6577]

Damn these are the best tutorials

[@nicolascrochet4093]

Amazed by this video. Thanks

[@user-cq7yy8qw3i]

very nice explanation. keep it up

[@codemonk9]

Great tut, thx

[@int4_t]

underrated

[@tushartilwani9540]

Awesome!

[@Ghasakable]

Sorry I have a question about your explanation here, in 5:13min precisely, I thought the macro `println` is a function that will own s1, and it has its own scope, if that is correct, then s1 will be deallocated first, then s2, while you refer to the end of the scope by the end of the bracket? is my understanding correct? or something I missed here? again, I am very much thankful for the effort of making such an amazing explanation video. This will not change the fact of what you have stated, but just for my understanding, thank you very much.

[@Ghasakable]

I found the answer here: The macros print!, println!, eprint!, eprintln!, write!, writeln! and format! are a special case and implicitly take a reference to any arguments to be formatted. These macros do not behave as normal functions and macros do for reasons of convenience; the fact that they take references silently is part of that difference.

[@IngridPuppet]

Thank you.

[@eddyecko94]

Thanks

[@nezman_x2080]

5:12 the code throws an error because S1 ownership passed down to S2 and the compiler will execute an error message.

[@MOUNIROU60]

thnx for the video

[@thanoscar8709]

BIG NOOT!