This is an excellent video! It really helps you understand the WHY's of different memory management techniques in Rust. Many Rust videos explain how to do things, but very few explain why to do things. This video is a must watch if you really want to understand Rust under the covers. Well done!
Thank you for your work. This video clarified many questions I had about memory alignment and helped me to understand how Rust is able to perform some optimizations, such as using a single usize for storing an Optional RC and Box. Keep up the good work!
Thank you for your work, this is I think the best video I've seen about this subject and the first time I clearly understand the memory management in Rust. Clearly a video all people learning rust should watch. Really nice explanations on why things work like this and not just how. If you could do a video about async rust / Tokio that would be awesome !
This is the best rust explanation video in the world. I would give anything if there also is an in-depth look at the concepts of functional programming in rust explained like in this video because those concepts are crucial to understand rust and I'm still struggling to understand them.
very good video! first time I really understood how stuff works behind the scenes! especially with rust enums - I didn't know it's like a union maybe do a follow up video on interior mutability, that'll be really interesting!
Personally I find this video extremely valuable @Sreekanth not just for Rust for compiled languages internals. Question I have what is the font used ? It looks like Jetbrains Mono but with some font ligatures turned on. Not sure what are the values
Excellent video. I just wish animation of the stack to show chunks of memory allocated like a stack (one on top of the other) and freed the same way. I find it more intuitive.
- For this one, I used powerpoint to generate the video. For all other videos in this channel, I use github.com/ManimCommunity/manim. - Audio is generated with TTS service in Azure. Combined both with Davinci Resolve. - Subtitles with timings can be generated with github.com/m1guelpf/auto-subtitle (minor corrections will be needed).
35:10 probably not true, because the same example not compiles, if use something meaningful like println, not drop upd. i mistaken, seems like thats because of using println
Actually, at 19:10 you've made an incorrect amend. Trait objects are in fact DSTs, that was correct. Remember you can't create an array or slice of trait objects - [dyn Trait] - or receive one as a parameter - fn func(x: dyn Trait) - or use `self` in a Trait method, because each Trait implementation will have a different size. What do have known sizes are owned trait objects - e.g. Box and other smart fat pointers - and references to trait objects - &dyn Trait.
i don't understand why can't slices be allocated on the stack? in c++ they do and i think it's the same in rust also are sou sure that enums store index for each element? in c++ variants only the index of the alternative is stored which is enough to denote the type of the underlying union.
Better yet, do you have a written version of this with embedded images of the diagrams in this video? -This is quite informative, but the generated voice's intonation is making it difficult to pay attention or process the information given.-
![Visualizing memory layout of Rust's data types [See description/first comment]](http://i.ytimg.com/vi/rDoqT-a6UFg/mqdefault.jpg)
![Visualizing memory layout of Rust's data types [See description/first comment]](/img/tr.png)
I genuinely think this video should be included in The Rust Book. It is an absolutely incredible resource. Thank you Sreekanth!!! This is amazing.
Agree 100%
This video should be part of "The Rust Book". This really explains why rust has so many data types. We need more rust videos. Thank You Sreekanth 👏👏
This is an excellent video! It really helps you understand the WHY's of different memory management techniques in Rust. Many Rust videos explain how to do things, but very few explain why to do things. This video is a must watch if you really want to understand Rust under the covers. Well done!
Thank you for uploading with better audio. I could not stand the voice of the other version, but this one is alright to listen to.
Great video!
Please do this extended explanation also for containers such as deque hashmap btreemap etc. Thank you for effort put in this video.
This video should be seen by more people!
Thank you for your work. This video clarified many questions I had about memory alignment and helped me to understand how Rust is able to perform some optimizations, such as using a single usize for storing an Optional RC and Box. Keep up the good work!
Thank you for your work, this is I think the best video I've seen about this subject and the first time I clearly understand the memory management in Rust. Clearly a video all people learning rust should watch. Really nice explanations on why things work like this and not just how. If you could do a video about async rust / Tokio that would be awesome !
Thanks for updating the audio!
Thank you so much for reuploading
Incredible video, thank you very much!!
This is the best rust explanation video in the world. I would give anything if there also is an in-depth look at the concepts of functional programming in rust explained like in this video because those concepts are crucial to understand rust and I'm still struggling to understand them.
Amazing content, please do more rust themed deep dives
The first 20 minutes is valuable to anyone who writes software in any language. Love this!
Fantastic content. Nothing fancy, just straight to the point.
Great explanation.
This was INSANELY helpful. Thank you so much! 🙏🙏🙏
this video is just amazing!!!
very good video! first time I really understood how stuff works behind the scenes! especially with rust enums - I didn't know it's like a union
maybe do a follow up video on interior mutability, that'll be really interesting!
Wow, thanks a lot! This is very well done! Great visualizations and explanations 😊
Personally I find this video extremely valuable @Sreekanth not just for Rust for compiled languages internals. Question I have what is the font used ? It looks like Jetbrains Mono but with some font ligatures turned on. Not sure what are the values
I use github.com/be5invis/Iosevka
This was great
Excellent video. I just wish animation of the stack to show chunks of memory allocated like a stack (one on top of the other) and freed the same way. I find it more intuitive.
An amazing video....
What a genius this man is...Where did you learn so much thing?
This is cool. Can you tell us what you used for animating these graphics and the text? Also what audio generator is used here?
- For this one, I used powerpoint to generate the video. For all other videos in this channel, I use github.com/ManimCommunity/manim.
- Audio is generated with TTS service in Azure. Combined both with Davinci Resolve.
- Subtitles with timings can be generated with github.com/m1guelpf/auto-subtitle (minor corrections will be needed).
35:10 probably not true, because the same example not compiles, if use something meaningful like println, not drop
upd. i mistaken, seems like thats because of using println
very very helped me. thanks a lot🎉🎉
around 11:00 isn't it a move instead of copy?
it’s a copy in memory level. Move is a compile level thing.
Thank you so much bro.
Actually, at 19:10 you've made an incorrect amend. Trait objects are in fact DSTs, that was correct. Remember you can't create an array or slice of trait objects - [dyn Trait] - or receive one as a parameter - fn func(x: dyn Trait) - or use `self` in a Trait method, because each Trait implementation will have a different size. What do have known sizes are owned trait objects - e.g. Box and other smart fat pointers - and references to trait objects - &dyn Trait.
Is this presentation available anywhere?
i don't understand why can't slices be allocated on the stack? in c++ they do and i think it's the same in rust
also are sou sure that enums store index for each element? in c++ variants only the index of the alternative is stored which is enough to denote the type of the underlying union.
terminator is teaching us rust.
Better yet, do you have a written version of this with embedded images of the diagrams in this video?
-This is quite informative, but the generated voice's intonation is making it difficult to pay attention or process the information given.-
Most of this is covered in the book "Programming Rust"
@@sreekanthpr Thank you!
subbed 4 this 1
i love this video so much
do you have sources for this material?
Rust 💟
Reupload with different automated voice?
Yea. I feel this audio is better compared to the one in the first video.
What’s the reason you don’t narrate it yourself?
@@sreekanthpr I agree, this voice is way less noisy and more natural
@@MrHirenP I would also like to know
@@MrHirenP maybe he has health issues, maybe he's insecure, maybe his english pronunciation isn't good. doesn't matter, he's posting excellent content
autoread got just promoted to the next level lol
26:00 very important gotcha!
but , what's going on, what's your next video about rust ?
Your are goat.
Wow
Very useful, could you do a video on zig allocators?
how is this gonna fix my divorce