command-line-rust
nextest
command-line-rust | nextest | |
---|---|---|
38 | 16 | |
1,297 | 1,954 | |
- | 2.1% | |
7.0 | 9.8 | |
5 days ago | 2 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
command-line-rust
-
Best path to learn rust
You absolutely must write programs, preferably using tests to ensure you are creating correct and reproducible code. May I suggest starting with my book, Command-Line Rust (O'Reilly, 2022). All the code/data/tests are in https://github.com/kyclark/command-line-rust Note that there are branches showing how to use the 4.x version of clap (command-line argument parser) rather than the 2.33 that was current when the book was published.
-
How to start learning a systems language
I think the best way to start learning a programming language is to write lots of small programs that you probably already know. Rust is a perfect command-line language, so I think it makes sense to start by implementing simple programs like "head" and "grep." I also think one should always learn to write and run tests, so I present my GitHub repo of inputs and tests you might like to use to write 14 such standard Unix command-line utilities: https://github.com/kyclark/command-line-rust If you want guidance on the language, I wrote a book called Command-Line Rust (O'Reilly, 2022) that explains all this code. One caveat is that the "clap" (command-line argument parser) module was at 2.33 when I published but is now v4, so you should look at the appropriate branches for versions of the programs that use the "builder" and "derive" patterns for that module. Or just use any old command-line parser you like as there's no requirement to use "clap." Best of luck to you!
-
What is the best way to learn Rust from a complete beginner programmer?
You must write programs in a language in order to learn it. I also firmly believe that learning how to write and run tests is critical to learning any language. I wrote Command-Line Rust (O'Reilly, 2022) for the beginner (in Rust, at least) and with a focus on writing and testing small programs from very simple "Hello, world!" and getting increasingly more complex. You can look at https://github.com/kyclark/command-line-rust for the code/inputs/tests. Best of luck!
-
Questions about moving from Bash to Rust
Code for the above book
-
Stuck at 4.3 of the rust book. It's so hard for me.
I'm the author of Command-Line Rust (O'Reilly, 2022), which I wrote to introduce the language slowly to beginners by writing and testing short, focused programs. You can look over the code/tests/data at https://github.com/kyclark/command-line-rust. Note that there are branches that show the same programs using a more recent version of the "clap" crate.
- Disappointing experience with 'Command-Line Rust': Seeking more comprehensive Rust resources
-
How do i get started with rust as my first language. I need tips and useful advice from rustians thanks.
I wrote Command-Line Rust (O'Reilly, 2022) to guide beginners in the language. You are challenged to write small functions and programs using tests to verify that everything is correct. You can look over the code and tests at https://github.com/kyclark/command-line-rust. Best of luck in your journey!
-
Learning rust by example
Here are the example programs from my book, Command-Line Rust (O'Reilly, 2022), along with the input files and tests: https://github.com/kyclark/command-line-rust
-
How to Practice and Learn Rust for Production Level Code?
I like to suggest that students write programs they already know (or at least understand). For instance, you probably understand that head shows the first few lines of a text file, and you probably can already implement some version of that in one or two languages you know. Try that in Rust. I wrote 14 BSD/GNU command-line utilities in Rust for learning purposes. I wouldn't consider these high-performance/production programs as they are tailored to learning the language. I also stress how to test programs, so there are tests and inputs you can use to verify your programs match the output of the original programs (or you can modify these to suit your own tastes for how you would like them to work). https://github.com/kyclark/command-line-rust
-
Error handling in a CLI app
Here are some more examples you may or may not find useful: https://github.com/kyclark/command-line-rust I tend to have a main() that calls a library's run() function that returns a Result and then exit with a nonzero code and error message on a failure.
nextest
-
Rust Tooling: 8 tools that will increase your productivity
cargo-nextest describes itself as a “next-generation Rust test runner”. To install, you need to run cargo install cargo-nextest.
-
My favourite Git commit (2019)
> On my work I make 1-15 commits a day. If I have to spend thought cycles on the commit message, that is time that goes from other productive endeavours.
I make roughly that many commits a day as well. If something's easy to understand I'll put in a simple commit message (e.g. [1]), but I do put in the effort for more complicated ones.
[1] https://github.com/nextest-rs/nextest/commit/efd194b2e1d8d61...
[2] https://github.com/oxidecomputer/omicron/commit/b07a8f593325...
-
Rust tech stack
If you need fancier testing than what's built into Rust, cargo-nextest is becoming quite popular.
-
Customizable testing framework
https://nexte.st/ is what is getting all the attention as a replacement test harness/framework these days.
-
Hey Rustaceans! Got a question? Ask here (11/2023)!
I believe cargo-nextest supports running separate binaries concurrently.
-
Fellow Rust enthusiasts: What "sucks" about Rust?
Do you already use nextest or something else? That really leans into test parallelism and sounds like a perfect fit for how you structure the tests.
- Альтернативний спосіб запускати тести
-
buffer-unordered-weighted: a variant of StreamExt::buffer_unordered where each future has a weight
I built it for cargo-nextest, in service of a new feature where some tests can be marked as heavier than others.
-
Small changes you can make in a rust codebase that have a significant impact
IMO 100% worth checking out: https://nexte.st/
-
Why does Rusts testing tools seem so much less polished compared to its other tooling?
For me, most of my needs are covered with next-test(https://nexte.st/), not that I have ever used any of the things you mentioned 😅
What are some alternatives?
argparse - Argument Parser for Modern C++
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
code - Source code for the book Rust in Action
cargo-limit - Productivity improvements for Rust ecosystem: warnings are skipped until errors are fixed, LSP-independent Neovim integration, etc.
book - The Rust Programming Language
cargo-deny - ❌ Cargo plugin for linting your dependencies 🦀
pico-args - An ultra simple CLI arguments parser.
shadow-rs - A build-time information stored in your rust project.(binary,lib,cdylib,dylib)
pipe-rename - Rename your files using your favorite text editor
Cargo - The Rust package manager
bat - A cat(1) clone with wings.
TestNG - TestNG testing framework