This solved lots of misunderstandings I had about Rust. It should be placed right in the documentation of the language (at least a link, so one could find it easily and early on the rust book)

@MrEnsiferum77

Жыл бұрын

Maybe the ownership is different, but everything else is school thing explained here.

@dreastonbikrain1896

Жыл бұрын

@@MrEnsiferum77 could you point me to a program or a book where theese things are taught to people?

This was extremely enlightening in visualizing rust's memory model. Thank you for taking the time to create this!

Just remember about the memory layout of things like structs. You CANNOT rely on the memory layout or ordering of fields to be a certain way, as it's not defined how it will end up. If you need to rely on this, you need to use things like `#[repr(C)]`. In fact, not even the tuple struct's memory layout is guaranteed. To guarantee it, you would need to use `#[repr(transparent)]`

This is not just a great video for Rust developers, but a great introduction for all developers into the process' memory layout and workings of the operating system!

@notsojharedtroll23

Жыл бұрын

Fax

*UPDATE: This video is re-uploaded with a better audio here* kzread.info/dash/bejne/aZOjj7uLqMnFk8Y.html Corrections: * 6:10, it should be 2^64 - 1 (without parenthesis) * Trait is dynamically sized. Trait object has known size.

@dersebastianbauer

2 жыл бұрын

28:22 this isn't precise. Gargabe collection (as in JS, Go or Java) does not keep track of refernces. In its cleanup run GC just checks wether there is a reference to this memory or not and after it is finished it forgets about it. Your description fits more to automatic reference counting used by Objective-C and Swift.

@shumudu5377

2 жыл бұрын

by which software are the pictures drawn?

@sreekanthpr

2 жыл бұрын

@@shumudu5377 For this video, I used Powerpoint. For all other videos in this channel, I use manim library (Python).

@parry84

2 жыл бұрын

at 28:10, I suppose the indices should be 0, 1, 2 instead of 0, 2, 3. btw great video, thanks you ❤

@noop9770

Жыл бұрын

* trait objects are dynamically sized types, meaning that their size is known at runtime. Pointer types to trait objects are sized at compile-time but have twice the size of pointers to sized types. Correct me if i got something wrong

Incredible explanation, it makes it so much easier to understand compiler errors when you have this video and memory mapping in mind. Thanks !

I was looking for info on dynamically sized types, but I found so much more in the video. One of the clearest explanations for such confusing concepts in Rust. Great video!

Wow, I really love this. Nice refresher of multiple topics even for someone who is intermediate-advanced rust user.

This is awesome! I didn't know that I needed this that badly! Thanks for sharing this great work!

Extremly well delivered information with not a single wasted second. Very good work!

A nice overview and/or refresher.

Hats off for making everything clear🙌 You're extremely talented. You're able to explain things logically by providing reasons. Thanks❤️

The best video on vtable , Smart pointers, trait object..Awesome job. Thanks

Thanks for this. It is brilliant!

I was confused about box, rc, and arc until now. Thanks!

Nice work! Hope to see more Rust videos from you.

Definitely the best Rust video on KZread. I will keep this video and watch again and again! 감사합니다🙏

This video will remain as the best go-to video for new rustaceans! Excellent work Sreekanth!!!

Genuinely, thank you SO much for this video. I was banging my head against a wall trying to PRECISELY understand fat pointers, why str is a primitive type, and other low-level questions

Great explanation. Love to see more such deep dive video about Rust.

Rust is the way forward and this is a great piece of work. Thanks.

This video is gold. Thanks for the hard work!

Dude, amazing work! Just amazing

Beautiful, I'd consider the topics covered here to be required knowledge, and the video is a nice way to present things that can be difficult to visualize.

Very useful and nice depiction of memory layout of each data type. It should be placed right inside the documentation

This is very clear and great explanation on rust memory management. thanks for the explanations

finally I've understood strings in rust. thank you a lot!

This is gold! Congrats :)

This is gold! Thank you.

Easy to understand video for complex concepts. Thanks for sharing.

@malharvora1281

2 жыл бұрын

It would be awesome if you put more Rust-related videos with the same level of explanation. IMHO there are a lot of videos of Rust internals available on KZread but only a few like this, are actually understandable by novice Rustaceans.

Your video helped me a lot. Thank you.

Really appreciate this video, thank you

Visualization helps a lot, thanks!

Wow, honestly incredible

extremely well done video!

This video help me understand rust memory a lot , thanks ~

Thank you! this was very helpful.

Great explanation! Thanks

This is golden, thanks!

thank you for sharing knowledge. appreciate the effort.

Such wisdom, oh great one.

Enlightening! Thank you!

damn i cannot imagine its the day that i will truly understand how memory handled by kernel and OS, just by clicking video about RUST HAHHAA

Great video. I wanted to check out Rust for use in userspace applications, however the types seemed too high level and convoluted to me, since I primarily program in C. This video helped visualize the types and allows me to think of them in a more familiar C like way and visualize them in memory. I feel like every languages needs videos like this, as it makes mechanisms within the language more explicit and easy to understand in simpler terms.

Thank you man for sharing this stuff

bruh I loved this video. thanks for your great content.

very informative! thank you

Wonderful. So thorough.

Great lecture, but in the future, consider asking a friend to narrate! I know a lot of people don’t like posting themselves online, but many people would probably be happy to help out! :)

Thank a lot, this makes learning Rust a lot easier. The less magic the better.

great work, very helpful for me

this is the best video I have ever watched on youtube

Jesus Christ. This is so awesome explanation. Thanks to you I can be now understanding how stack and heap grows up

Awesome explaination

This is so useful! Thanks

the best introduction has ever seen.

I recently started with rust and holy shit i can'ttell how helpful this was

Thank you Sreekanth. Coming from a C background, this really helped me understand what Rust is about.

need more videos like this

awesome explanation 👏👏👏👏👏

Amazing video! Would be awesome if you made more videos like this for Rust

This is exactly i want. Thank you!

This is high quality stuff!

The best video!!! Thnx

That was very useful 👍

Thanks!!! Your video is too good

This video is beautiful

very good and clear

love to learn thanks for sharing

We rustacean loved it! you should create more videos about rust, like this one!

This is the best explain to Rust

Bro this was so cool, loved the video even tho it was with an AI voice, usually dont like those but the content was NOICE

good stuff, thank you very much

Amazing video thanks.

This makes so much more sense! Could you please cover RefCell?

love it help me a lot i hope you do cargo next!

thank you for this

This is worth more than some of computer arch classes at university.👍

I cannot thank you enough 🙏

Super! Thanks

this is the best memory video ever made. I downloaded it because of fear to lose it if youtube servers shut down or volcano, earthquake, meteor or something... lifesaving enum memory tip @23:55

just beca a subscriber keep up the good work Sir.

holy shit this was amazing

The mention of "malloc" made me think of the assertions around self-compiled language aspects, something I first remember hearing about with Pascal, then C. I presume then this does not include the libc and some other libraries, or perhaps just not always. I guess if it is a clang compilation, by implication, it's not self-compiled, so perhaps the assertion is it is self-compiled in some environments, or that some copies are self-compiled, or that the core of the compiler is self-compiled, but not all the libraries it uses.

you are brilliant ser :)))))))))))))

24:30 The malloc implementation will have some overhead (at least 8 bytes) in managing the extra heap allocation.

thanks

awesome, cool

so freakin good

Great ty ty

Is it possible to make borrow-checker to take care of individual structure fields? I mean I want to pass the whole structure mutable reference in/out for functions, but to make the borrow-checker to care about what fields has been modified. Is it?

Awesome

O Captain! My Captain! Are you going to publish a book? I think we need more lectures for memory dynamics.

Great video, thanks! At 6:10, there is an error for the address range. The caption reads 2^(64-1), which is incorrect, as it implies 2^63 because of the parenthesis. The parens either needs to be removed, or put around the exponent to be correct.

@sreekanthpr

2 жыл бұрын

Thank you. Happened during the final subtitle edits. It was written in words for generating the sound in the original text.

Is this documented somewhere? Where did you find the info to make the video? Awesome video by the way.

@sreekanthpr

2 жыл бұрын

Rust specific things are mostly from the book "Programming Rust" (mentioned in video description)

Great watch so far. Questions @8:45 shouldn't the main stack frame allocate the `b` variable before entering the `add_one` function?

@sreekanthpr

2 жыл бұрын

yes

@urbex9797

2 жыл бұрын

In practice, yes. But really, no, it's not necessary. The compiler can even decide to reuse the space previously used by `a`. Because at that point, `a` is no longer used.

It is a cool video. Not only for Rustaceans.

Very good

Thanks! What tts do you use?

@sreekanthpr

Жыл бұрын

Microsoft one note >> View >> Immersive reader

why does the kernel add some paddings in memory when storing enums. I know it's to have the same size for every enum type. but why do we have to have the same size?