cargo-watch VS tarpaulin

I used cargo-watch here so that every time my source changes, the server will automatically restart and re-serve the updated code.

watch-one-test test_name: # More info on cargo test: https://doc.rust-lang.org/cargo/commands/cargo-test.html # More info on cargo watch: https://github.com/watchexec/cargo-watch cargo watch -x check -x 'test -- --test-threads=1 --nocapture {{test_name}}' -c -q

Rust: RPDS https://docs.rs/rpds/latest/rpds/ and Im https://docs.rs/im/latest/im/

Rust isn’t great for letting you do FP things like other languages, but it does have the best type system imho which makes it the leading functional programming language right now imho. If you’re not using too many specialized python packages then I recommend using Rust instead, even for toy demos, as you can be more confident your code works without needing to run it and wait for a crash like you would in debugging python, and the tests also run faster in rust due to the incremental compilation. Use cargo-watch and you can retest your code every time you save your work.

https://github.com/watchexec/cargo-watch

I usually write a make command to cargo watch and rerun each test file : code file pair independently so then you won’t rerun your tests in other modules when you change the one you work on (faster but might miss stuff if you change API contracts which touch other parts of your codebase)

you can use cargo-watch to real time run tests on save in your attached vs code console session which is about as close to what you're asking as I think exists for rust

Note that cargo, by virtue of being a package manager for a programming language, is primarily going to be dealing with library packages. That's not because it can't manage executables (see cargo-watch for a particularly useful example), it's just that it's less common.

Also check out cargo-watch -- https://crates.io/crates/cargo-watch

Unless there's a new issue, I think this is what was here: https://github.com/watchexec/cargo-watch/issues/249

A feature that I look for whenever possible in my development environment is Hot Reload, with it, every time a file is changed and saved the application restarts, so the cycle of writing-evaluating-refactoring code becomes extremely fast, for Rust, we have cargo watch, I suggest taking a look at the documentation for more details.

I’ll add tarpaulin, a crate I use for code coverage analysis.

Any pros/cons compared to tarpaulin?

What about tarpaulin : https://github.com/xd009642/tarpaulin

Note that the tool cargo-tarpaulin provides code coverage.

There is https://github.com/xd009642/tarpaulin for code coverage, but I'm not sure how widely it's used.

I know giving a link is not a tutorial, but I use https://github.com/xd009642/tarpaulin for this.

Writing software test for [Toql](https://crates.io/crates/toql) and shaking out smaller bugs here and there. [Tarpaulin](https://github.com/xd009642/tarpaulin) is such a fantastic tool!

Code quality also has become quite better than the last year. Almost codes in the project are tested by either unit or integration tests. Code coverage using tarpaulin is above 90%.