cargo-watch
bacon
cargo-watch | bacon | |
---|---|---|
22 | 25 | |
2,615 | 1,441 | |
0.8% | - | |
6.7 | 8.0 | |
4 months ago | 18 days ago | |
Rust | Rust | |
Creative Commons Zero v1.0 Universal | GNU Affero General Public License v3.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.
cargo-watch
-
Cryptoflow: Building a secure and scalable system with Axum and SvelteKit - Part 0
I used cargo-watch here so that every time my source changes, the server will automatically restart and re-serve the updated code.
-
Use just to manage Rust project commands
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
-
Functional Programming 1
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)
-
Are there any continuous testing tools with real-time line-by-line IDE feedback for Rust?
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
-
Why does the "crate" nomenclature include both "binary" and "library"?
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.
-
Help me love Rust - compilation time
Also check out cargo-watch -- https://crates.io/crates/cargo-watch
-
cargo-watch hangs on reload
Unless there's a new issue, I think this is what was here: https://github.com/watchexec/cargo-watch/issues/249
- Cargo Watch 8.3.0
- Cargo Watch v8.2.0
-
Creating Rest APIs with Rust
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.
bacon
- Bacon – a background Rust code checker
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
Probably one of the biggest speed ups to your inner loop writing / running code is to use something like https://github.com/Canop/bacon/. I used a combination of the docs and GPT chats to increase my learning speed a lot.
-
Project Diagnostics
Nice, I'll have a look. I miss having bacon in a tmux split, wish TS had something like that.
-
Report on platform-compliance for cargo directories
As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.
-
What's your current Vim+Rust setup?
bacon + nvim-bacon
-
What are some useful tools for Rust?
bacon
-
Are there any continuous testing tools with real-time line-by-line IDE feedback for Rust?
I love cargo-watch and still it use it situationally, but as a companion to my editor workflow I mostly switched to bacon. Being able to switch with one keystroke to another cargo subcommand is delightful.
-
What is your number one rust tool?
Try bacon for checks & test!
-
Alternative to watch -cq
Was it bacon perhaps?
- Something similar to Rust's `bacon` tool but for Python?
What are some alternatives?
cargo-check
rust - Empowering everyone to build reliable and efficient software.
cargo-multi - Extends cargo to execute the given command on multiple crates - upstream is at
cargo-geiger - Detects usage of unsafe Rust in a Rust crate and its dependencies.
cargo-count - a cargo subcommand for counting lines of code in Rust projects
helix - A post-modern modal text editor.
cargo-script - Cargo script subcommand
miri - An interpreter for Rust's mid-level intermediate representation
Cargo - The Rust package manager
darkfi - Anonymous. Uncensored. Sovereign.
cargo-outdated - A cargo subcommand for displaying when Rust dependencies are out of date
config - configuration.nix is better than dot files