cargo-llvm-cov
Cargo subcommand to easily use LLVM source-based code coverage (-C instrument-coverage). (by taiki-e)
| cargo-llvm-cov | totally-safe-transmute | |
|---|---|---|
| 9 | 17 | |
| 821 | 245 | |
| - | - | |
| 9.3 | 0.0 | |
| 15 days ago | over 1 year ago | |
| Rust | Rust | |
| Apache License 2.0 | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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-llvm-cov
Posts with mentions or reviews of cargo-llvm-cov.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-25.
-
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
totally-safe-transmute
Posts with mentions or reviews of totally-safe-transmute.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-20.
-
Sudo Replacement
For example, there is this (pure safe Rust) code: https://github.com/ben0x539/totally-safe-transmute/blob/main... which accesses external resources (/proc/self/mem) in order to violate the safety guarantees.
-
A rust crate that lets you compress ASCII text to a single Unicode "character"
The first is the totally_safe_transmute crate. I mean, who wouldn't love library code that has .expect("welp") and .expect("oof") as its error handling? But that's not even the really scary part. Issue #2 ("i hate this") remains open to this day, but for obvious reasons there's no chance of resolution. This post has some context and a line-by-line explanation of how it works.
-
What do you expect from Rust in 2023?
You mean like this?
-
In C# you can transmute without `unsafe`
You can also do that in rust on linux: https://github.com/ben0x539/totally-safe-transmute/blob/master/src/lib.rs
-
Why choose Rust
I want to correct this statement: Rust can be safer, but not if a library you use contains unsound code. Unsoundness is most often caused by unsafe code, but not always (totally_safe_transmute, anyone?). There is a misconception that unsafe code blocks are always unsound and should be avoided at all costs, but they're completely fine if the safety contracts are upheld. In fact, unsafe blocks isolate the potential issues to make it easier to identify where undefined behavior may be occurring. unsafe code blocks are a feature of the language, and their usage should not be viewed as opting out of any safety the language provides, imo.
-
"# NONONONONONO DON'T YOU FUCKIN' DARE the safety features are there so that your programs aren't filled to the brim with security vulnerabilities. Unless you care A LOT(And I mean A LOT A LOT) about compile times, never use `unsafe`."
Just reimplement totally_safe_transmute in Zig. No need for unsafe.
-
I mean, it solves most library conflicts
Why transmute() when you can totally_safe_transmute()?
- Safe Transmute
-
Static Analyzer Rudra Found over 200 Memory Safety Issues in Rust Crates
Well, there is always the totally-safe-transmute.
-
// SAFETY: NO
They should use https://github.com/ben0x539/totally-safe-transmute
What are some alternatives?
When comparing cargo-llvm-cov and totally-safe-transmute you can also consider the following projects:
grcov - Rust tool to collect and aggregate code coverage data for multiple source files
tinyvec - Just, really the littlest Vec you could need. So smol.
tarpaulin - A code coverage tool for Rust projects
tamago - TamaGo - ARM/RISC-V bare metal Go
rustfix - Automatically apply the suggestions made by rustc
rust - Rust language bindings for TensorFlow
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
usbarmory - USB armory - The open source compact secure computer
cargo-expand - Subcommand to show result of macro expansion
advisory-db - Security advisory database for Rust crates published through crates.io
cargo-temp - A CLI tool that allow you to create a temporary new Rust project using cargo with already installed dependencies
UnsoundCrates - Black list of all crates that promotes unsoundness
cargo-llvm-cov vs grcov
totally-safe-transmute vs tinyvec
cargo-llvm-cov vs tarpaulin
totally-safe-transmute vs tamago
cargo-llvm-cov vs rustfix
totally-safe-transmute vs rust
cargo-llvm-cov vs cargo-msrv
totally-safe-transmute vs usbarmory
cargo-llvm-cov vs cargo-expand
totally-safe-transmute vs advisory-db
cargo-llvm-cov vs cargo-temp
totally-safe-transmute vs UnsoundCrates