Check out the full Rust programming playlist! 🦀 kzread.info/head/PLDbRgZ0OOEpUkWDGqp91ODn0dk7LPBAUL

Would have loved to see in this video concepts like `Fn`, `FnOnce`, when to use `move`, and function items vs pointers vs fn traits.

The quality of your camera and the mic is sick and your tutorials are brilliant. Well done.

@TrevorSullivan

4 ай бұрын

Wow, thank you!! I'm glad you are learning from my channel!

The best Rust closure tutorial on KZread. Well done, Trevor!

@TrevorSullivan

2 ай бұрын

Thank you Simon! I hope you're enjoying the Rust language! 🦀

And I finally got closures

@TrevorSullivan

7 ай бұрын

Nice!!! They're not hard after all, right? 🙂🦀

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.

@TrevorSullivan

Ай бұрын

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. 😊

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?

@TrevorSullivan

2 ай бұрын

Thanks for the comment! I have a video on Rust iterators. Were you looking for something else?

Very well explained. Thank you so much❤

Really straightforward, great video!

Thank you. It’s a tough language to wrap your head around

// 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.

@mohsan5491

Ай бұрын

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

@TrevorSullivan

Ай бұрын

That's interesting! Thanks for sharing.

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?

@TrevorSullivan

2 ай бұрын

Hmmm I'll have to see if that's possible with the Rust Analyzer extension!

bro im over here nesting closures inside modules .... You are a great tutor Please Dont Stop Making theese videos !!!!

Another banger thanks sgain !!!

Really Good Explanation !

Thanks, your tutorial is easy to understand

Brilliant content, thank you!

clear, concise, amazing

@TrevorSullivan

2 ай бұрын

@abdushakoor0099 Thank you for your kind comment! What other Rust topics are you interested in?

@abdushakoor0099

2 ай бұрын

@@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.

@TrevorSullivan

2 ай бұрын

@@abdushakoor0099 That's actually something that I want to do, yes! Thank you for the suggestion.

@abdushakoor0099

2 ай бұрын

@@TrevorSullivan amazing

Loved the tutorial

Well explained

Fantastic

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!

@TrevorSullivan

3 ай бұрын

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! 🚀

@benjaminpowell1508

3 ай бұрын

@@TrevorSullivan Thanks, I'll check that out!

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

@TrevorSullivan

8 ай бұрын

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?

@ThisGuyDakota

8 ай бұрын

@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

@TrevorSullivan

8 ай бұрын

​@@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.

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! :)

Liked and subscribed

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 ??

@TrevorSullivan

7 ай бұрын

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.

Can I suggest that you turn off your IDE's inline hints, or at least change the font and style. At the moment there is little to distinguish what you have typed as the code from what your editor is producing. For example, whether the colon in the closure parameters is explicitly typed, or inferred, is merely a matter of whether the color is purple or white. Anyone unfamiliar with how you have your particular IDE configured will not know what's what.

@TrevorSullivan

3 ай бұрын

Thanks for the feedback, Andy. I agree that the Rust Analyzer extension can make the inline type hints look like actual code. I need those type hints in order to write code effectively though. Maybe I can do a better job of calling out this fact in my videos.

@andyk2181

3 ай бұрын

@@TrevorSullivan Looking at my own editor, I have the hints enabled, but they appear in gray so are more distinct from the code I've written. Perhaps you are using a high-contrast theme? Anyway, thanks for the video.

is it just me who finds rust syntax sexy

@TrevorSullivan

3 ай бұрын

Haha you're definitely not the only one! It's different, but it has grown on me!

@teefus1

Ай бұрын

mee!

Php is already too generic in its own genetic :) php interfaces easily sustains that intension. Other langs generialize their structure with generics.