cargo-msrv
cargo-llvm-cov
cargo-msrv | cargo-llvm-cov | |
---|---|---|
11 | 9 | |
752 | 821 | |
- | - | |
9.1 | 9.3 | |
4 days ago | 12 days ago | |
Rust | Rust | |
Apache License 2.0 | 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.
cargo-msrv
-
Introducing cargo-ft: a cargo extension for specifying supported targets for a crate
What this tool say? https://github.com/foresterre/cargo-msrv
-
What’s everyone working on this week (19/2023)?
I'm working on cargo-marv.
-
What's your crate's Minimum Supported Rust Version?
Before getting overcome by despair, have a look at cargo-msrv -- this little gem of a tool figures it all out for you!
-
What's everyone working on this week (31/2022)?
I'll be adding a 'minimal' output format to cargo-msrv for use in scripts. I'll also be updating the book, and inch closer towards releasing v0.16.
-
Rust for the Kernel Could Possibly Be Merged for Linux 5.20
First commit 2 months ago, started with edition 2021. https://hg.sr.ht/~cyplo/legdur/browse/Cargo.toml?rev=ca11815...
Have you tried compiling something less than bleeding edge, with a year old compiler, or are you picking projects specifically to "showcase" the supposed failings of the Rust compiler?
Many libraries in the ecosystem have a MSRV (minimum support rust version) guarantee, with compile-time shims to enable newer features if a more recent version is detected.
You can pin your dependencies to those versions (and if they don't have an explicit MSRV, just pin it to a version by date or by running https://github.com/foresterre/cargo-msrv on the project to find the effective MSRV).
You can cargo install specific versions of a binary crate, and if they move to the 2021 edition, or use a recently stabilized standard library function or w/e, you can simply choose to install a specific version, that would work with your distro's rustc/cargo.
I'm not even talking about the completely valid, but last resort strategy of many non-bleeding edge distro package maintainers, of simply creating a .patch file and applying it. In legdur's case, --- edition = "2021" +++ edition = "2018" on Cargo.toml would probably do the trick. For libraries/binaries you control, you can use https://doc.rust-lang.org/cargo/reference/overriding-depende... and https://github.com/itmettkeDE/cargo-patch.
Giving up after the first minor roadblock and crying bloody murder is intellectually lazy.
-
[Gitoxide in January]: full multi-index support in object database and complete git-index reading
Looks helpful though it doesn't seem to address when you don't have a Cargo.lock. I've created an issue for this.
-
What’s everyone working on this week (8/2022)?
I'll be switching over the CLI of cargo-msrv, from Clap's builder methods to the attribute macro. I hope this will simplify the configuration, as my Config and ConfigBuilder structs (which were build from Clap's ArgMatches) was growing fast, and becoming slightly unorganized. With the attribute macro, the config will be constructed directly by code generated by the macro. The mostly saves one intermediate step, and a lot of boilerplate.
- cargo-msrv v0.14.0 release
-
Announcing `cargo supply-chain`: Know whom you trust
Some combination of cargo-outdated and cargo-msrv could probably do this in a slightly more manual fashion.
cargo-llvm-cov
-
TIL about `cargo llvm-cov` and `cargo nextest`
I'll let them speak for themselves: https://github.com/taiki-e/cargo-llvm-cov https://nexte.st/index.html
- Code coverage beyond lines?
-
What do you expect from Rust in 2023?
Meanwhile I wholeheartedly recommend https://github.com/taiki-e/cargo-llvm-cov which makes it almost as simple.
- Kudos to cargo-llvm-cov - really useful coverage reporting
-
Code Coverage Tooling
And the options to fail on insufficient coverage are rather lacking supporting only line coverage. I have suggested improvement and might do it if there is interest from the author.
-
Measuring the coverage of a Rust program in Github Actions
Another alternative is https://github.com/taiki-e/cargo-llvm-cov which is easy to use. Don't forget to also try the --html flag with it.
-
Website similar to cppinsights.io for Rust visualization
I'd take a look at either https://github.com/taiki-e/cargo-llvm-cov and/or https://github.com/dtolnay/cargo-expand for this kinda of behavior.
- cargo-llvm-cov: Cargo subcommand to easily use LLVM source-based code coverage
What are some alternatives?
toml-bombadil - A dotfile manager with templating
grcov - Rust tool to collect and aggregate code coverage data for multiple source files
crates.io-index - Registry index for crates.io
tarpaulin - A code coverage tool for Rust projects
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
rustfix - Automatically apply the suggestions made by rustc
rust_lisp - A Rust-embeddable Lisp, with support for interop with native Rust functions
cargo-expand - Subcommand to show result of macro expansion
competitive-programming-rs - Algorithm Snippets for Competitive Programming in Rust
cargo-temp - A CLI tool that allow you to create a temporary new Rust project using cargo with already installed dependencies
pdc
rustviz - Interactively Visualizing Ownership and Borrowing for Rust