really love the cheatsheet! is there any chance a v2 is planned (simply a bit more readable / good looking / maybe dark themed?) Thanks for your videos! loving it
Honestly speaking this is probably the single most confusing aspect of Rust I faced, much more so than the whole ownership thing. I think it might be down to how little attention it was given in various Rust learning resources (Rust Book in particular). It took me several months of scratching my head and smushing my face into the screen, combined with extensive experimenting on my personal projects for me to fully understand the whole system, and you sir managed to do it under 20 minutes. God damn. Mad respect.
Oh, man, you saved me! I was about to give up and head back home because I was overwhelmed by the complexity of these modules. But then I stumbled upon you, and now I feel like I'm back in a playground, ready to tackle anything
This is by far the best explanation of Rust module system I've seen (or read) so far. Very thoroughly explained. I've reentered the Rust orbit after almost two years again and had forgotten about the intricacies of the Rust module concept in the mean time. Now I feel like I am back on track again. This video is pure gold. Thanks!
A great video, that's cleared the a major point of confusion up for me. It's like 'use' has been overridden, like 'static' in C - for external module use, it's 'importing' and 'simplifying' external crate components, whereas for local modules it's merely 'simplifying' part of the local module. So subtly different actions, but with the same name. You've clarified that for me, so thanks!
Yeah, the modules did confuse me a lot. During this video I was thinking: "Oh, okay, now I finally get it. How great he explains it so clear." and then I remember that the video is actually called "Explained Like I'm 5". Now I feel I have to study programming as if I was five :-D
God, thank you. I was so confused about modules. Having read dozens of documents about this topic getting even more confused. Now everything makes sense.
Thank you. I think that this video is much more informative than the module episode of the rust book series and the chapter of the rust book itself!! I was bugged thinking about a module not "export itself" but being declared in the parent module
You're a legend. Learning Rust as my first coding language and am going to binge watch your videos to help accelerate the process. Thank you so much for taking the time to put these videos together 🙌🏾🙏🏾🔥
I was reading Chapter 7 of the Rust Book and found the example a little confusing so I searched for an alternative source of information abuot modules in Rust. This was just what I needed. Thank a lot Rusty!!!
This is the best explanation that I have found so far. Rust modules were a little bit confusing because they work differently from how organisation of code world in other languages.
THANK YOU for this! Modules finally clicked for me! Request: a similar video (or videos) breaking down Cargo crates. For example, crates with multiple binaries and projects with nested Cargo configs.
So the only things crate consumers can use from a crate are items in the crate module marked pub? The items marked pub in sub-modules are only pub for the crate module, and need to be explicitly "re-pub'd" from the crate module to also be made available to the crate consumer?
👍Great job! I'd like to learn more about benchmarking/profiling of Rust code. Another thing that is confusing is why we need to write anon lifetime specifier _ (underline) . I see it in very often in trait/struct decl/def.
awesome video. this is what I want to know. there are some minor differences then javascript but rust's module system is more effective and sense I think.
Nice video! Now I finally understand the Rust modules and project structure. As there are 2 approaches mentioned in this video to struct the modules and project files, may I know which one approach is more popular or is most used in the practice? Thanks a lot!
Hi! Please include this video in the let's get rusty tutorial series. It's really helpful in visualizing the module system, especially the refactoring approach you took. And exploring the 2018 pattern (came across this in the wild and I was quite confused )
Okay, convoluted conventions but once understood they make sense and feel clean and powerful enough to maintain code properly factored and under control. Thanks a lot for making this video, it was a day saver!
Kindly cover some (design) patterns in how to export rust functions to swift and kotlin via FFI. Thank you, your video on rust modules is very helpful.
Really well described! I'd love if you could make a video about async/await as well as how it differs from its implementation in more popular languages like Javascript. This topic has always been tricky to wrap my head around. I think a lot of viewers would benefit from a solid explanation LGR style :)
It seems in 2023, you need to run " cargo modules --with-types --with-fns " to get the same output as shown in the video. Went on a detour trying to see why my output differed and that was the result.
It would be nice if you cover cross development and debugging for the Raspberry Pi and it would also be nice to cover using Rust for embedded systems (no runtime), for example on Arduino.
2:31 How to setup VSCode to move automatically text cursor with indentation after pressing enter inside curve brackets? Is it rust-analyzer settings option?
In my project, when I added more folder branches within 'src', the local code worked normally (build, fmt, test). But when I executed the same in the CI/CD process, it was as if I couldn't find the imports in that format...
Now that I think of it, is there a VSC extension/configuration for sorting and files in the tree regardless of their type? In order to group the modules with their sub-modules..
If you try this today, you need to install cargo-modules using this command: cargo install cargo-modules --locked. It won't work any other way. It needs to install a million things and some of those things don't play nice together dependency wise. Also, the command to use to generate the try with types is now: cargo modules generate tree --types, The author(s) of cargo-modules have seemingly introduced several feature breaking changes on top of creating the dependancy nightmare that makes dll hell pale in comparison.
Still it doesn't expain how can I add even more directory depth to it. I'm experienced C++, GO, Python developer, even after this video I have no idea how to structure my code
I kinda stuck on a problem where I can't make traits use the pub keyword when they are inside a module (so kinda want to use inheritance as to what i have learned in php). Like the animal human example in rust where traits are implemented. But seems like my approach is kinda wrong. I happen to watch the video about builder pattern and it seems pretty much "fixed" my problem. It pretty much avoid you of having creating a struct that only one value is different but almost have the same methods.
I'm a bit confused with re export. In a nutshell does it mean making nested modules functions, structs etc... within your project src public for use at the top level, so anyone can use the function? Like a public interface?
hey, I have installed cargo modules. but when I run the command as like your command. its not showing me similar result to your. it just show mod and struct and enum. what the problem here.
Hey , I the cargo modules "generate tree --with-types" is not working. I have tried it by "generate tree --no-types" though its not showing as per the result in the video. Anyone help ?
📝 Get your FREE Rust cheat sheet : www.letsgetrusty.com/cheatsheet
I got mine, tho I don't like mailing lists too much :/
Loving the cheat sheet..i keep open on a tab always
indeed, I would have liked to checked it out, but don't want to sign up to anything
really love the cheatsheet! is there any chance a v2 is planned (simply a bit more readable / good looking / maybe dark themed?)
Thanks for your videos! loving it
Hate the signup mailing list. So skipped the cheatsheet.
Honestly speaking this is probably the single most confusing aspect of Rust I faced, much more so than the whole ownership thing. I think it might be down to how little attention it was given in various Rust learning resources (Rust Book in particular). It took me several months of scratching my head and smushing my face into the screen, combined with extensive experimenting on my personal projects for me to fully understand the whole system, and you sir managed to do it under 20 minutes. God damn. Mad respect.
Yeah, same here.
This!!!!
Same :) This video is absolutely awesome!
me too!!
Thanks God I was able to find the video in only a week of smashing the face into the screen...
I have read many blogs before getting the gist of the module system of rust. Actually the only thing I needed was this video lol
It's nice that you've kept the format of videos on fundamentals similar to your coverage of the rust book, it's like having an extended version!
Oh, man, you saved me! I was about to give up and head back home because I was overwhelmed by the complexity of these modules. But then I stumbled upon you, and now I feel like I'm back in a playground, ready to tackle anything
This is by far the best explanation of Rust module system I've seen (or read) so far. Very thoroughly explained. I've reentered the Rust orbit after almost two years again and had forgotten about the intricacies of the Rust module concept in the mean time. Now I feel like I am back on track again. This video is pure gold. Thanks!
I've googled "ho to use modules in Rust" so so many time. It is a pleasure to see such a useful, straight forward explanation on that topic.
loop { 👍}
Excellent video! Really appreciate how you broke this down.
A great video, that's cleared the a major point of confusion up for me. It's like 'use' has been overridden, like 'static' in C - for external module use, it's 'importing' and 'simplifying' external crate components, whereas for local modules it's merely 'simplifying' part of the local module. So subtly different actions, but with the same name. You've clarified that for me, so thanks!
Yeah, the modules did confuse me a lot. During this video I was thinking: "Oh, okay, now I finally get it. How great he explains it so clear." and then I remember that the video is actually called "Explained Like I'm 5". Now I feel I have to study programming as if I was five :-D
lol
God, thank you. I was so confused about modules. Having read dozens of documents about this topic getting even more confused. Now everything makes sense.
Thank you. I
think that this video is much more informative than the module episode of the rust book series and the chapter of the rust book itself!!
I was bugged thinking about a module not "export itself" but being declared in the parent module
Perfect screen size / text. Great video.
You made these easy for me to understand. Now I understand how Rust's module system works. thank you.
You're a legend. Learning Rust as my first coding language and am going to binge watch your videos to help accelerate the process. Thank you so much for taking the time to put these videos together 🙌🏾🙏🏾🔥
Rust is not the easiest way to learn coding, but it will certainly help you in the long run. Good luck !
Wathed 3 tuturials. This one clearly stands out! 👍
I was reading Chapter 7 of the Rust Book and found the example a little confusing so I searched for an alternative source of information abuot modules in Rust. This was just what I needed. Thank a lot Rusty!!!
Nice and detailed explanation of a confusing subject in Rust! I'll still have to play around a bit...but this was really insightful !
Many might already have said this, but this was the achilles heel of my rust experience so far...
Thank you very much for making this video!
This is the best explanation that I have found so far. Rust modules were a little bit confusing because they work differently from how organisation of code world in other languages.
you've got a subscriber! exactly what i needed! was with that strange feeling you've mentioned while reading The Book, now it feels clear.
As a JS developer I need more videos like this. Thanks
Excellent pace of the video. These videos are perfect as I try to learn and start using Rust!
THANK YOU for this! Modules finally clicked for me!
Request: a similar video (or videos) breaking down Cargo crates. For example, crates with multiple binaries and projects with nested Cargo configs.
The best explanation about Rust´s module system I got! This is all really confusing, but now it seems to make some sense 😊 Thank you!
That's precisely what i needed, a simple, concise and comprehensive explanation. Now i got it, thanks a lot!
So the only things crate consumers can use from a crate are items in the crate module marked pub? The items marked pub in sub-modules are only pub for the crate module, and need to be explicitly "re-pub'd" from the crate module to also be made available to the crate consumer?
Very good explanation!
Modules should be explaind again and again beacuse they are vital part of rust encapsulation approach.
👍Great job! I'd like to learn more about benchmarking/profiling of Rust code. Another thing that is confusing is why we need to write anon lifetime specifier _ (underline) . I see it in very often in trait/struct decl/def.
I bet this will be your most popular video in 5 years time. Graet job.
Thank you!
AMAZING explanation and step-by-step tutorial, thank you!
Your explaination was perfect! Great job
One of the most important and useful videos in Rust learning. Many thanks!
HOLY COW , this is TEH hands down best explenation on the net for Rust Newcommers! This Explains Use vs Mod perfect! Thank you so much!
awesome video. this is what I want to know. there are some minor differences then javascript but rust's module system is more effective and sense I think.
Nice video! Now I finally understand the Rust modules and project structure. As there are 2 approaches mentioned in this video to struct the modules and project files, may I know which one approach is more popular or is most used in the practice? Thanks a lot!
Thank you for this quick explanation, much appreciated.
This is such a helpful channel whenever I try to learn a bit more about rust thank you!
Really nice well rounded and concise presentation, thanks!
Hi! Please include this video in the let's get rusty tutorial series. It's really helpful in visualizing the module system, especially the refactoring approach you took. And exploring the 2018 pattern (came across this in the wild and I was quite confused )
Okay, convoluted conventions but once understood they make sense and feel clean and powerful enough to maintain code properly factored and under control.
Thanks a lot for making this video, it was a day saver!
Well explained, the best rust youtube channel.
Kindly cover some (design) patterns in how to export rust functions to swift and kotlin via FFI. Thank you, your video on rust modules is very helpful.
I am getting into programming and learning Rust, I think it's pleasantly elegant!
Great video and channel in general, you answered all my questions i had.
Awesome , Clear understanding ❤ Thanks for this video 🎉
man! your content is even better than the rust docs for sure!
you got yourself a new subscriber :D
Great video that helps a lot in understanding the concept of modules in Rust
Well done. This is exactly what I needed!
Really well described! I'd love if you could make a video about async/await as well as how it differs from its implementation in more popular languages like Javascript. This topic has always been tricky to wrap my head around. I think a lot of viewers would benefit from a solid explanation LGR style :)
Great topic! Took something that can be difficult to understand and presented it in a simple step by step presentation! My favorite!
This is such impressive teaching. Good job.
cool - now I am able to structure my code into models. Thank you.
It would be fine to learn something about testing in Rust.
It seems in 2023, you need to run " cargo modules --with-types --with-fns " to get the same output as shown in the video.
Went on a detour trying to see why my output differed and that was the result.
It would be nice if you cover cross development and debugging for the Raspberry Pi
and it would also be nice to cover using Rust for embedded systems (no runtime), for example on Arduino.
Amazing Video. Out of so many I've watched on this topic, this is the one that made everything click for me. Thank you
Good stuff. The chapter in the Rust book needs this sort of example-based explanation as well as comparisons to other languages lol
Rust Made Easy with Let's Get Rusty! you made it really easy to understand!
Very very very useful!!! Next could you please cover conditional compilation, build flags, build.rs, etc.? Thanks a lot
Great tutorials. Can you list down or make a video on which extensions do you use in VSCode for Rust. Many thanks in advance
clear and concise explanation
Amazing. this was really helpful and concise
Perfectly explained, cheers.
2:31 How to setup VSCode to move automatically text cursor with indentation after pressing enter inside curve brackets? Is it rust-analyzer settings option?
It would be awesome if you did some videos on async/await
On the list!
bro, your video is so good. I have know the concept of rust modules. Thanks very much.
Thank you so much for this great content, this is very valuable for me!
What's up rusty! everything fine? Came here to complete one more monster video about Rust! Thank you for sharing your knownledges with us.
RUST ❤
In my project, when I added more folder branches within 'src', the local code worked normally (build, fmt, test). But when I executed the same in the CI/CD process, it was as if I couldn't find the imports in that format...
Now that I think of it, is there a VSC extension/configuration for sorting and files in the tree regardless of their type? In order to group the modules with their sub-modules..
Something I often wonder about, does it speed up compile time if you split up your project in multiple modules?
This concept is really easy to understand on small projects, but I would still love to see a bigger project example
"Submodules must be declared in the parent module" omg that explains my confusion. I think I should put this as a sticky note on my monitor
Finally ! Bogdan thank you for this. Rust Yedi !
omg, I couldn't put my finger on it... You're right. He's the chosen one. ;)
Can I ask what keyboard you have? It sounds so good!
Would one recommend this same structure used for libraries in applications as well?
If you try this today, you need to install cargo-modules using this command: cargo install cargo-modules --locked. It won't work any other way. It needs to install a million things and some of those things don't play nice together dependency wise.
Also, the command to use to generate the try with types is now: cargo modules generate tree --types, The author(s) of cargo-modules have seemingly introduced several feature breaking changes on top of creating the dependancy nightmare that makes dll hell pale in comparison.
It did install for me without appending the --locked flag, but the subcommands are totally different
Man I wished this video existed before I struggled to make sense of modules.
thanks man, this is really great video.
thank you, very well explained!
I did not understand the last part about exporting credentials. Rest of the section were 🔥
great explanation, thanks a lot!
Still it doesn't expain how can I add even more directory depth to it. I'm experienced C++, GO, Python developer, even after this video I have no idea how to structure my code
I kinda stuck on a problem where I can't make traits use the pub keyword when they are inside a module (so kinda want to use inheritance as to what i have learned in php). Like the animal human example in rust where traits are implemented. But seems like my approach is kinda wrong. I happen to watch the video about builder pattern and it seems pretty much "fixed" my problem. It pretty much avoid you of having creating a struct that only one value is different but almost have the same methods.
This video is pure gold!
Nice job. In IntelliJ I find it convenient to just create modules in line and then tell IntelliJ to turn them into separate files.
I'm a bit confused with re export. In a nutshell does it mean making nested modules functions, structs etc... within your project src public for use at the top level, so anyone can use the function? Like a public interface?
Happy new year bro cheers!! 🍻
Happy new year!
Could u make a video sharing abt professional exp and y u r moving to RUST !!
hey, I have installed cargo modules. but when I run the command as like your command. its not showing me similar result to your. it just show mod and struct and enum.
what the problem here.
the "if let Status::Connected" line prevents me from compiling your code, "error[E0658]: `let...else` statements are unstable"
Thank you so much for this!
why is it like this tho is there a good reason to have it designed like this? why not be bound by folder path?
This was much easier to understand than the official book.
Seeing someone do it while talking through it is a big help.
Please make a video on
Emacs + Rust
best rust channel out there
Are there changes in module system with 2021 edition ?
Amazing, thank you very much!
You explications are very good! Thanks for aclarate this topic.
Hey , I the cargo modules "generate tree --with-types" is not working. I have tried it by "generate tree --no-types" though its not showing as per the result in the video.
Anyone help ?