I am just getting started with the clap crate and your video is very educative! Keep up the great work! Actually I very much like the approach you take in all of your videos where you basically walk us through the crate docs, then continue with a couple of examples and at the same time explaining and showing specific functions used in that crate. Then repeat all of this back and forth until you get your result - that is what real world programming is! Even in the AI era where people start to rely more and more on copilots for autocompletion without having a look at the docs, I firmly believe that if one wants to keep up with latest and greatest versions of most of the packages, he/she needs to have this fundamental skill. Thank you for being here for all of us, I am enjoying your style and videos a lot!
Agreed, that does look confusing. It's just indicating the closing line for a particular block. They should highlight that differently. Might be good feedback for the Rust Analyzer extension.
It may be your theme that does it - you should be able to tweak it if you pull up the json for that specific theme and have a poke around (most colours are in groupings etc) and they’d be inlay hints or something along those lines. (I use them via rust and have turned them on for Python recently too with strict typings, they come up as a grey for me after some tweaking (a little lighter than commented code)
At time 14:10, when adding a new position argument, the type hint “Command” looks like it is part of the code. This threw me off so much I went back to the Rust book thinking I missed some builder/macro syntax where chaining doesn’t require a period “.” - hope you can get to update the color/font settings on the type hints but otherwise awesome video!
Awesome video! - Is there a way to reuse an arg without redefining it twice. Let’s say both person and pet require an address. Can I make one address argument and attach it to both register-person and register-pet?
Thanks Haydn, and great question! I'd have to test to see if you can assign an argument configuration to a variable and reuse it. If you try this and find out, please do share!
@@TrevorSullivan yes - it does work! let first_name_arg = Arg::new("firstname"); let m = Command::new("My Program") .about("Explains in brief what the program does") .arg(&first_name_arg) .subcommand(Command::new("subcmd") .about("This is a sub command") .arg(&first_name_arg) ) .get_matches();
Fantastic content, and I've enjoyed some of your other tutorials too. One thing: please don't be running as the "root" user and installing stuff as the "root" user. Even if this is a throw away VM only ever used for this exercise, it's very bad practice, and I wouldn't want any other viewers/subscribers to think this is an ok thing to do. It's not. Other than that grumble, this was just what I was looking for and you've earned another subscriber - thank you for all your work!
is there a way to declare a flag for example: -s. Without needing to add some value to it? When i pass the -s in my program i just need to show all infos so i dont need a variable assigned there. I just can do it with -s show for example
Great question, it looks like there is a way to do that. Check out this link stackoverflow.com/questions/60458705/how-do-i-specify-a-boolean-command-line-flag-using-clap
You’re rust videos are really awesome. Do you have a patreon or can I donate to you in another way? Also regarding topics for future videos, I would like to propose “how to build your application to please the borrow checker” As a beginner I often ended up in situations where I didn’t know how to design something in rust to please the borrow checker. E.g. in C I just declare some global variables to Hold my command line arguments. In rust you have clap and you have the command line arguments in a struct most oft the times in the scope of the main function. How to you make the argument struct available to all functions? I use to pass it to every function at least as a borrow. But that seems kind of unelegant.
Thank you very much! I do have a PayPal page, and any donations would be graciously accepted! This content isn't sponsored or compensated, other than Google's tiny ad revenue. paypal.me/pcgeek86 As far as passing arguments to functions go, I would think that borrowing the arguments from your main function makes sense. That would be a good topic for end-to-end application building someday!
I imagine part of the point of having to pass everything around is to sort of force people to use dependency injection instead of having little factories everywhere?
![ลองสุ่มไอโฟน 990 โกงมั้ย? [ โกงมั้ยครับ ep.101 ] | DOM](http://i.ytimg.com/vi/bfsWe0j492k/mqdefault.jpg)
i have watched so many courses on rust but no one gives the refrence of the topic and explanation but you explain well , thanks you men
I am just getting started with the clap crate and your video is very educative! Keep up the great work! Actually I very much like the approach you take in all of your videos where you basically walk us through the crate docs, then continue with a couple of examples and at the same time explaining and showing specific functions used in that crate. Then repeat all of this back and forth until you get your result - that is what real world programming is! Even in the AI era where people start to rely more and more on copilots for autocompletion without having a look at the docs, I firmly believe that if one wants to keep up with latest and greatest versions of most of the packages, he/she needs to have this fundamental skill. Thank you for being here for all of us, I am enjoying your style and videos a lot!
Thanks so much for sharing your thoughts! I'm glad you're benefitting from these videos on Rust! Keep learning! 🦀🧠
Awesome job, man! You helped me so much. God bless you my friend! You deserve much more recognition, keep going.
Great stuff! one small thing though, the VS code type hints are really confusing in white.
Agreed, that does look confusing. It's just indicating the closing line for a particular block. They should highlight that differently. Might be good feedback for the Rust Analyzer extension.
It may be your theme that does it - you should be able to tweak it if you pull up the json for that specific theme and have a poke around (most colours are in groupings etc) and they’d be inlay hints or something along those lines.
(I use them via rust and have turned them on for Python recently too with strict typings, they come up as a grey for me after some tweaking (a little lighter than commented code)
At time 14:10, when adding a new position argument, the type hint “Command” looks like it is part of the code. This threw me off so much I went back to the Rust book thinking I missed some builder/macro syntax where chaining doesn’t require a period “.” - hope you can get to update the color/font settings on the type hints but otherwise awesome video!
This tutorial is really helpful. I was really having a hard time learning CLAP. You made it very easy. Thanks ❤❤
exactly the video i needed! thank you!
I have searched for such a good tutorial for a long time, thanks a lot!
Derive approach is the declarative way. Builder is imperative.
Thanks for the clap tutorial!
Very tangential, but what is that microphone you're using. I love the way it looks and sounds.
Hello! It's the MXL 990. I agree, it sounds great! I do have some EQ settings applied as well.
Thank you very much!!!
Great explanation. Do you plan to cover the Derive pattern of clap?
Thank you!! That's not necessarily a high priority topic for me, but I can add it as an idea to my backlog! I appreciate the suggestion 🙂
Very helpful. Good job.
Awesome video! - Is there a way to reuse an arg without redefining it twice. Let’s say both person and pet require an address. Can I make one address argument and attach it to both register-person and register-pet?
Thanks Haydn, and great question! I'd have to test to see if you can assign an argument configuration to a variable and reuse it. If you try this and find out, please do share!
@@TrevorSullivan yes - it does work!
let first_name_arg = Arg::new("firstname");
let m = Command::new("My Program")
.about("Explains in brief what the program does")
.arg(&first_name_arg)
.subcommand(Command::new("subcmd")
.about("This is a sub command")
.arg(&first_name_arg)
)
.get_matches();
This is such a well-made video. Keep it up
Seriously amazing tutorial!!
This video is useful.
Fantastic content, and I've enjoyed some of your other tutorials too. One thing: please don't be running as the "root" user and installing stuff as the "root" user. Even if this is a throw away VM only ever used for this exercise, it's very bad practice, and I wouldn't want any other viewers/subscribers to think this is an ok thing to do. It's not. Other than that grumble, this was just what I was looking for and you've earned another subscriber - thank you for all your work!
Really enjoying your work 😊❤
Thank you! ❤️ I'm glad you're learning Rust! 🦀
Thanks for the tutorial man! :D
is there a way to declare a flag for example: -s. Without needing to add some value to it? When i pass the -s in my program i just need to show all infos so i dont need a variable assigned there. I just can do it with -s show for example
Great question, it looks like there is a way to do that. Check out this link stackoverflow.com/questions/60458705/how-do-i-specify-a-boolean-command-line-flag-using-clap
@@TrevorSullivan ok thx man
@@TrevorSullivan ok now it works, I was trying to use takes_value() which is no longer avaliable, using num_args(0) works fine
Thanks for your video ! It was very useful !
your videos are really helpful, thx my friend
Excellent.
Super Solid!!! Thanks a lot man
You’re rust videos are really awesome. Do you have a patreon or can I donate to you in another way?
Also regarding topics for future videos, I would like to propose “how to build your application to please the borrow checker”
As a beginner I often ended up in situations where I didn’t know how to design something in rust to please the borrow checker.
E.g. in C I just declare some global variables to
Hold my command line arguments.
In rust you have clap and you have the command line arguments in a struct most oft the times in the scope of the main function. How to you make the argument struct available to all functions? I use to pass it to every function at least as a borrow. But that seems kind of unelegant.
Thank you very much! I do have a PayPal page, and any donations would be graciously accepted! This content isn't sponsored or compensated, other than Google's tiny ad revenue. paypal.me/pcgeek86
As far as passing arguments to functions go, I would think that borrowing the arguments from your main function makes sense. That would be a good topic for end-to-end application building someday!
I imagine part of the point of having to pass everything around is to sort of force people to use dependency injection instead of having little factories everywhere?
I never did understand making an optional mandatory.
thank you
nice
👏👏👏
Which IDE are you used in this video ?
@TrevorSullivan
It's VSCode with the Rust Analyzer extension! Check out my first video in the Rust playlist, on my channel. It covers my environment setup!
Easily one of the most poorly documented crates I've encountered.
@@liminal27 yeah I struggled a lot with it before creating this video. There's documentation, it's just hard to comprehend.
@@TrevorSullivan I started using ChatGPT to help fill in gaps eg. "what does [code snippet] mean?" and it so far it's been great.
coding using `root` account? The man has no fear.
Completely glossed over the most important part of this whole tutorial... how did you open up the emoji selector.
@@EmbeddedSorcery WIN + PERIOD 😊
.arg(Arg::new("fluffy")
.long("fluffy")
.help("are they a furry?")