I was thinking the same thing. Its not clear at all why capturing something changes the closure type from Fn to FnOnce - I would intuitively think that only happens in move closure that capture by value and then return that captured value.
I've seen many rust videos before and I'd never seen your channel being mentioned, which is surprising, given the quality of your content. I'll definitely watch a lot of other videos about rust in your channel. Thanks for the content!
Like the way you cover the material, thanks. Disappointed not to find a video on the second half of the chapter in the Rust book, though. Are you planning on doing iterators?
The IDE filling in phantom types with a similar font and color to the rest of the text was hard to read. add(x: -3, y: -5); gave me an error lol. Maybe keep them off by default and flash them with a hotkey when you want to show what Rust is seeing?
Hey Trevor, Thanks a ton for this Rust course playlist! Your effort truly shows in the high quality content. It's made learning Rust much clearer and enjoyable. Really appreciate your work.
Thank you! I appreciate your kind comment and I'm very happy that this has helped you. That's all I hope to accomplish, making other people's lives better, by sharing knowledge. I hope you benefit from viewing code in crisp 4k. 😊
// In VSCode, type inference for a closure looks like this: let print_number: impl Fn(u16) = |n: u16| println!("incoming: {0}", n); // However, in RustRover, the inferred type for the same closure is presented as: let print_number: fn(u16) = |n: u16| println!("incoming: {0}", n); Interesting how different IDEs handle Rust's type inference for closures. VSCode uses impl Fn(u16) to indicate a flexible closure that might capture the environment, while RustRover opts for fn(u16), suggesting a simpler, non-capturing function pointer. It's a neat insight into the nuances of Rust's type system and how tooling can vary in presenting it.
when I tried to expicitly type "let print_number : impl Fn(u16)=" analyser did not complained but compiler threw this error error[E0562]: `impl Trait` is not allowed in the type of variable bindings --> src/closures.rs:2:24 | 2 | let print_number : impl Fn(u16) = |n: u16| println!("incoming: {0}", n); | ^^^^^^^^^^^^ | = note: `impl Trait` is only allowed in arguments and return types of functions and methods
Hmm, very nice explanation, but there is perhaps more to be said in this interesting subject. What about function generator with closured variables? What about counters... randomizers... mixers.... and what is FnOnce ??? I think we all would love to see what you can tell about those topics. Closures are quite advanced tbh, but well, that's the time to learn I guess! :)
Trevor, I'm new to Rust and your videos have really helped, thank you. I was just wondering what VS setting you have enabled to get the errors/warnings to show up inline. I think this would be helpful. Thanks!
Hey Benjamin, thank you for joining me on the Rust journey! I have a video in the playlist that talks about setting up the Rust development environment. You'll want to install the Rust Analyzer extension for VScode. Keep on learning! 🚀
This is one of those topics I never understood in any language lol (this and recursive functions) I kind of understand how they're used, but no idea what a potential use-case would be so it's hard to practice
After you spend a while learning the fundamentals, you can add in external libraries that allow you to build rich CLI apps, web APIs, games, and desktop applications. What are you interested in building?
@TrevorSullivan currently don't have a project in mind, just want to learn rust for the sake of learning rust. I'm heavily into PowerShell, and I've dabbled with Python and C# a while ago. Just want to learn some low-level stuff to get a better understanding of what my PowerShell might be doing behind the scenes I guess. If I had to pick a project, I'd say maybe like a pong game or something. Although a CLI tool of some sort might be easier since I wouldn't have to learn gui stuff yet lol
@@ThisGuyDakota Nice, I come from a PowerShell background as well. It's awesome, but struggles performance-wise at scale. Knowing how to code in a lower-level language will help you build more efficient apps that scale faster and handle larger volumes of data. Rust (seems) to be the perfect balance of performance and developer friendliness. It's not "easy," but it also guides you along very nicely. 🦀 Rust on! 🦀 Thanks for joining me on the journey. Check out the "ratatui" crate, by the way, for building CLI apps. I'll get around to recording a video about it eventually.
so lets say after calling change_name for the first time , then I want to execute so code that requires updated p1.last_name and I want call change_name , so am i not allowed to do that ??
In that case, one option would be to derive the Clone trait on the object, so you can call .clone() on it. That way, you would have a separate object in memory that can be borrowed independently from the object you're trying to mutate. There might be more efficient solutions than that, but that's the easiest mechanism that I'm currently aware of.
Check out the full Rust programming playlist! 🦀 th-cam.com/play/PLDbRgZ0OOEpUkWDGqp91ODn0dk7LPBAUL.html
Would have loved to see in this video concepts like `Fn`, `FnOnce`, when to use `move`, and function items vs pointers vs fn traits.
I was thinking the same thing. Its not clear at all why capturing something changes the closure type from Fn to FnOnce - I would intuitively think that only happens in move closure that capture by value and then return that captured value.
The quality of your camera and the mic is sick and your tutorials are brilliant. Well done.
Wow, thank you!! I'm glad you are learning from my channel!
for real. i don't know why i didn't find his channel before.
The best Rust closure tutorial on TH-cam. Well done, Trevor!
Thank you Simon! I hope you're enjoying the Rust language! 🦀
I've seen many rust videos before and I'd never seen your channel being mentioned, which is surprising, given the quality of your content. I'll definitely watch a lot of other videos about rust in your channel. Thanks for the content!
@@lcssbr thank you so much. That means a lot to me. I'm glad that my format is helpful for you! Keep learning Rust! 🦀
Like the way you cover the material, thanks.
Disappointed not to find a video on the second half of the chapter in the Rust book, though.
Are you planning on doing iterators?
Thanks for the comment! I have a video on Rust iterators. Were you looking for something else?
The IDE filling in phantom types with a similar font and color to the rest of the text was hard to read. add(x: -3, y: -5); gave me an error lol.
Maybe keep them off by default and flash them with a hotkey when you want to show what Rust is seeing?
Hmmm I'll have to see if that's possible with the Rust Analyzer extension!
I thought the same when I first started with rust, but you get used to it
Hey Trevor,
Thanks a ton for this Rust course playlist! Your effort truly shows in the high quality content. It's made learning Rust much clearer and enjoyable. Really appreciate your work.
Thank you! I appreciate your kind comment and I'm very happy that this has helped you. That's all I hope to accomplish, making other people's lives better, by sharing knowledge. I hope you benefit from viewing code in crisp 4k. 😊
THIS IS THE BEST CLOSURES EXPLANATION!
@@firstname-lastname I'm very happy to hear that this helped you understand closures! 🦀
bro im over here nesting closures inside modules .... You are a great tutor Please Dont Stop Making theese videos !!!!
// In VSCode, type inference for a closure looks like this:
let print_number: impl Fn(u16) = |n: u16| println!("incoming: {0}", n);
// However, in RustRover, the inferred type for the same closure is presented as:
let print_number: fn(u16) = |n: u16| println!("incoming: {0}", n);
Interesting how different IDEs handle Rust's type inference for closures. VSCode uses impl Fn(u16) to indicate a flexible closure that might capture the environment, while RustRover opts for fn(u16), suggesting a simpler, non-capturing function pointer. It's a neat insight into the nuances of Rust's type system and how tooling can vary in presenting it.
when I tried to expicitly type "let print_number : impl Fn(u16)=" analyser did not complained but compiler threw this error
error[E0562]: `impl Trait` is not allowed in the type of variable bindings
--> src/closures.rs:2:24
|
2 | let print_number : impl Fn(u16) = |n: u16| println!("incoming: {0}", n);
| ^^^^^^^^^^^^
|
= note: `impl Trait` is only allowed in arguments and return types of functions and methods
That's interesting! Thanks for sharing.
Thank you Trever, you're an awesome teacher :)
And I finally got closures
Nice!!! They're not hard after all, right? 🙂🦀
closure is easy. it's just that rust syntax is hard.
Did you mean, you finally found closure? ;)
Very well explained. Thank you so much❤
Hmm, very nice explanation, but there is perhaps more to be said in this interesting subject. What about function generator with closured variables? What about counters... randomizers... mixers.... and what is FnOnce ??? I think we all would love to see what you can tell about those topics. Closures are quite advanced tbh, but well, that's the time to learn I guess! :)
Really straightforward, great video!
28:15
You only can access p1 if you change twice. It's seems an bug, imagine how many bugs will happen with this "feature".. unhappy about rust....
Thank you. It’s a tough language to wrap your head around
great video man!!
Trevor, I'm new to Rust and your videos have really helped, thank you. I was just wondering what VS setting you have enabled to get the errors/warnings to show up inline. I think this would be helpful. Thanks!
Hey Benjamin, thank you for joining me on the Rust journey! I have a video in the playlist that talks about setting up the Rust development environment. You'll want to install the Rust Analyzer extension for VScode. Keep on learning! 🚀
@@TrevorSullivan Thanks, I'll check that out!
@28.00 for who do not understand println macro itself takes immutable reference of value it is supposed to print. hence the error
Another banger thanks sgain !!!
Really Good Explanation !
I learned so much. Thank you
That’s nice . But what is the purpose of using the closure if we just run it in the same scope . I really don’t find it useful in this case .
Fantastic
clear, concise, amazing
@abdushakoor0099 Thank you for your kind comment! What other Rust topics are you interested in?
@@TrevorSullivan i don't know if this will be out of scope of the content you make but making a TUI with rust kinda stuff.
@@abdushakoor0099 That's actually something that I want to do, yes! Thank you for the suggestion.
@@TrevorSullivan amazing
Thanks, your tutorial is easy to understand
Brilliant content, thank you!
This is one of those topics I never understood in any language lol (this and recursive functions)
I kind of understand how they're used, but no idea what a potential use-case would be so it's hard to practice
After you spend a while learning the fundamentals, you can add in external libraries that allow you to build rich CLI apps, web APIs, games, and desktop applications. What are you interested in building?
@TrevorSullivan currently don't have a project in mind, just want to learn rust for the sake of learning rust. I'm heavily into PowerShell, and I've dabbled with Python and C# a while ago.
Just want to learn some low-level stuff to get a better understanding of what my PowerShell might be doing behind the scenes I guess.
If I had to pick a project, I'd say maybe like a pong game or something. Although a CLI tool of some sort might be easier since I wouldn't have to learn gui stuff yet lol
@@ThisGuyDakota Nice, I come from a PowerShell background as well. It's awesome, but struggles performance-wise at scale. Knowing how to code in a lower-level language will help you build more efficient apps that scale faster and handle larger volumes of data. Rust (seems) to be the perfect balance of performance and developer friendliness. It's not "easy," but it also guides you along very nicely. 🦀 Rust on! 🦀 Thanks for joining me on the journey. Check out the "ratatui" crate, by the way, for building CLI apps. I'll get around to recording a video about it eventually.
Loved the tutorial
Well explained
It's more just code inserts which do not have a classical prologue and epilogue of a function.
great video thanks
so lets say after calling change_name for the first time , then I want to execute so code that requires updated p1.last_name and I want call change_name , so am i not allowed to do that ??
In that case, one option would be to derive the Clone trait on the object, so you can call .clone() on it. That way, you would have a separate object in memory that can be borrowed independently from the object you're trying to mutate. There might be more efficient solutions than that, but that's the easiest mechanism that I'm currently aware of.
Liked and subscribed