unsafe-code-guidelines
tarpaulin
unsafe-code-guidelines | tarpaulin | |
---|---|---|
74 | 12 | |
640 | 2,345 | |
1.3% | - | |
6.9 | 9.1 | |
about 2 months ago | 5 days ago | |
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.
unsafe-code-guidelines
-
Passing nothing is surprisingly difficult
Useful context on the Rust side is this issue [1]. It sounds like some of the author's concerns are addressed already.
[1]: https://github.com/rust-lang/unsafe-code-guidelines/issues/4...
-
Blog Post: Non-Send Futures When?
Is this captured by one of the known soundness conflicts? If not then should consider adding it to the list.
- Are crates like vcell and volatile cell still unsound?
-
Question: Are there things for Unsafe Rust learn from Zig?
There are some competing proposals for different memory models. Stacked borrows is the current proposal, but there are more work in the approproate WG.
-
Let's thank who have helped us in the Rust Community together!
Thank you /u/RalfJung for bringing formal methods to Rust, both through models like Stacked Borrows, by developing miri, and by working on unsafe-code-guidelines which aims to specify exactly what is and isn't allowed in unsafe code (surprisingly, it's an open question as 2023!)
- Questions about ownership rule
-
Noob Here: Why doesn't this work?
You could imagine some way to make this safe for example automatically convert &'short &'long mut T to &'short &'short T, but it's non-trivial to prove they are safe at all, not to mention ensuring this is correctly implemented in the compiler. If you're interested there's also a discussion on whether the opposite (& & T to & &mut T) is sound here.
-
When Zig is safer and faster than (unsafe) Rust
Agreed! MIRI is so good, it still feels like magic to me. It also comforts me that the Rust team takes improving unsafe semantics seriously, with the past Unsafe Code Guidelines WG and today's operational semantics team (t-opsem).
-
Safety and Soundness in Rust
I think there are some aspects of this rule that are still undecided. See for example:
- https://github.com/rust-lang/unsafe-code-guidelines/issues/8...
- https://github.com/rust-lang/miri/issues/2732
-
I wanna be a crab.
C is much better specified than unsafe Rust. Some things are just not worked out yet in Rust. This may sometimes even bite very experienced devs, such as this issue with Box's aliasing semantics, which tripped up the author of left-right.
tarpaulin
- Rust project test coverage
-
What are some good rust tools/extentions?
I’ll add tarpaulin, a crate I use for code coverage analysis.
-
Kudos to cargo-llvm-cov - really useful coverage reporting
Any pros/cons compared to tarpaulin?
-
Code Coverage Tooling
What about tarpaulin : https://github.com/xd009642/tarpaulin
- Measuring the coverage of a Rust program in Github Actions
-
Dare to ask for more #rust2024
Note that the tool cargo-tarpaulin provides code coverage.
-
Is there a rust way for doing TDD?
There is https://github.com/xd009642/tarpaulin for code coverage, but I'm not sure how widely it's used.
-
Uncovered Intermediate Topics
I know giving a link is not a tutorial, but I use https://github.com/xd009642/tarpaulin for this.
-
What's everyone working on this week (45/2021)?
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!
-
GlueSQL v0.7 - INDEX & ORDER BY are newly added.
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%.
What are some alternatives?
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
rust - Empowering everyone to build reliable and efficient software.
cargo-llvm-cov - Cargo subcommand to easily use LLVM source-based code coverage (-C instrument-coverage).
rfcs - RFCs for changes to Rust
proptest - Hypothesis-like property testing for Rust
x11rb - X11 bindings for the rust programming language, similar to xcb being the X11 C bindings
trust - Travis CI and AppVeyor template to test your Rust crate on 5 architectures and publish binary releases of it for Linux, macOS and Windows
bevy - A refreshingly simple data-driven game engine built in Rust
Racer - Rust Code Completion utility
miri - An interpreter for Rust's mid-level intermediate representation
cargo-watch - Watches over your Cargo project's source.