I tried. Building a simple cli tool to get a feeling for it for a bigger project. But then the “Rust by example” starts with installing clap as argument parser, which pulls 10 dependencies and LSP complains about not being able to build, because it doesn’t find a matching version, unless i do the implied version, but then it can’t derive features.
Now trying argparse, that was intuitive in python. And else getops. And else i try Safe-C or something.
Right now I am working on a Rust cli tool with clap and have no issues with the LSP in Neovim. It might be a configuration error. Clap is used by many and is the defacto standard cli parser in Rust. As a fan of argparse in Python, I think clap is even better. argparse being implemented as standard library is the biggest pro over clap. I wouldn’t even use getops anymore, unless it is a Bash script. And even so, Bash has its own builtin argument parser that I use for scripts.
If you really wanted to try Rust, you should sort of that issue. Clap works great and lot of users use it. Who knows, you may even end up liking it and Rust.
I explicitly only use it with features --derive. It let’s you write the cli option setup as a struct, which feels super natural to me. That’s why I know for a fact it works well. Look in your Cargo.toml under the section [dependencies] there should be an entry for clap: clap = { version = "4.5.41", features = ["derive"] } is mine. Right now version 4.5.48 is the newest I think.
Also from your previous reply, what do you mean “unless i do the implied version, but then it can’t derive features”? I don’t know why you shouldn’t be able to use derive. I’m no expert either BTW, just wondering what went wrong.
I tried. Building a simple cli tool to get a feeling for it for a bigger project. But then the “Rust by example” starts with installing
clapas argument parser, which pulls 10 dependencies and LSP complains about not being able to build, because it doesn’t find a matching version, unless i do the implied version, but then it can’t derive features.Now trying argparse, that was intuitive in python. And else getops. And else i try Safe-C or something.
Right now I am working on a Rust cli tool with clap and have no issues with the LSP in Neovim. It might be a configuration error. Clap is used by many and is the defacto standard cli parser in Rust. As a fan of argparse in Python, I think clap is even better. argparse being implemented as standard library is the biggest pro over clap. I wouldn’t even use getops anymore, unless it is a Bash script. And even so, Bash has its own builtin argument parser that I use for scripts.
If you really wanted to try Rust, you should sort of that issue. Clap works great and lot of users use it. Who knows, you may even end up liking it and Rust.
Edit: BTW which example do you refer to exactly? I looked at the official ones and couldn’t find: https://doc.rust-lang.org/stable/rust-by-example/
Thanks. Yeah, i’ll try again. The (Rust-)tooling is already selected for the bigger project anyway.
It’s from https://docs.rs/clap/latest/clap/ the
features --derive.I explicitly only use it with
features --derive. It let’s you write the cli option setup as astruct, which feels super natural to me. That’s why I know for a fact it works well. Look in your Cargo.toml under the section[dependencies]there should be an entry for clap:clap = { version = "4.5.41", features = ["derive"] }is mine. Right now version 4.5.48 is the newest I think.Also from your previous reply, what do you mean “unless i do the implied version, but then it can’t derive features”? I don’t know why you shouldn’t be able to use derive. I’m no expert either BTW, just wondering what went wrong.
Edit: typo