quickcheck
Clippy
Our great sponsors
quickcheck | Clippy | |
---|---|---|
13 | 120 | |
2,264 | 10,755 | |
- | 1.9% | |
4.0 | 10.0 | |
5 months ago | 6 days ago | |
Rust | Rust | |
The Unlicense | GNU General Public License v3.0 or later |
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.
quickcheck
- Declarative Rust macros explanation
-
Iterating on Testing in Rust
Maybe https://github.com/BurntSushi/quickcheck too?
-
Switching from C++ to Rust
Yeah as other have mentioned, I was using Rust before 1.0.
This is my first public commit: https://github.com/BurntSushi/quickcheck/commit/c9eb2884d6a6...
I didn't write any substantive Rust before that point. So I'm at over 9 years.
-
Hey Rustaceans! Got a question? Ask here (11/2023)!
The book, Zero To Production In Rust, uses quickcheck:
-
Reltester: automatically verify the invariants of PartialOrd/PartialEq/Ord/Eq handwritten implementations
Hi all! I'm looking for some feedback on my latest crate, reltester. It's a small utility crate that, when paired with property-based testing with e.g. quickcheck makes it very easy to check that your handwritten comparison trait implementations satisfy the necessary constraints (transitivity, reflexivity, and all that stuff). I wrote it our of frustration after finding many subtle bugs in our PartialEq and PartialOrd implementations at $JOB, and hopefully someone else will find it useful.
-
Code coverage beyond lines?
For what it's worth this would also be a good candidate for property based testing, like with: https://github.com/BurntSushi/quickcheck
-
Property-Based Testing in Rust with Arbitrary
I'm aware of Hypothesis and its approach, but the connection between Hypothesis and arbitrary is indeed non-obvious. Even looking over the API docs again, the most I could pick up was this on the docs of Unstructured:
- Automated property based testing for Rust
-
Rust is more portable than C for pngquant/libimagequant
Quickcheck https://github.com/BurntSushi/quickcheck
-
How can I reproduce this quickcheck error (and why is it happening)?
I'm running into a strange issue while using [quickcheck](https://github.com/BurntSushi/quickcheck) to implement tests and I'm hoping someone here might have an idea. Long story short, I have tests which fail in weird ways when using quickcheck that I can't reproduce otherwise, so I'm not even sure if it's a legitimate issue or not.
Clippy
-
More than you've ever wanted to know about errors in Rust
I couldn't find it in the API guidelines either. From what I understand, the idea is that any trait bounds, which includes generic type parameter bounds and lifetime bound on a type (struct or enum) would be repeated back in the impl block
there is a nice discussion on this issue here: https://github.com/rust-lang/rust-clippy/issues/1689
-
New clippy lint: detecting `&mut` which could be `&` in function arguments
You should not blindly follow clippy lints. They are sometimes wrong. Another example https://github.com/rust-lang/rust-clippy/issues/9782 .
- Let else will finally be formatted by rustfmt soon
-
My deduplication solution written in Rust beats everything else: casync, borg...
I often write () = f() to assert that f() is unit. Unfortunately clippy warns on such code ( https://github.com/rust-lang/rust-clippy/issues/9048 ). There are very recent pull requests for this bug, so hopefully this bug will be fixed very soon. But meanwhile I invented this workaround: [()] = [f()] :)
-
Any open source projects willing to take in juniors?
Apart from running clippy on many projects being essential, clippy is also an exceptionally welcoming project, no matter your prior knowledge.
-
Any new Opensource projects in (rust) looking for contributors. I want to start my journey as an OSS contributor.
clippy is a great place to get started :) though it isn't exactly new.
-
I want to contribute in a big project
clippy is also pretty compiler-adjacent and unlike rust-analyzer uses rustc's internal APIs. Don't let the size of the code base scare you off! It's actually feasible for a newcomer to contribute even such a substantial change as a new lint, and we have issues labeled as "good first issue" that come with mentorship, so you don't need to go it alone.
-
rustc-plugin: A framework for writing plugins that integrate with the Rust compiler
Yes, you could use it to write a lint. Although you might find it easier to just fork Clippy and add your own lints to their existing framework.
-
Reading Rust
Check out the readme for more information.
-
Rust Tips and Tricks #PartOne
They are two of my favorite Rust tools. If you haven’t tried them yet, I highly recommend giving them a try. Clippy can detect various lints in your code and guide you towards writing more idiomatic code. To install Clippy, simply run rustup component add clippy, and to run it within your workspace, execute cargo clippy. For more details, visit Clippy’s GitHub repository.
What are some alternatives?
proptest - Hypothesis-like property testing for Rust
rustfmt - Format Rust code
afl.rs - 🐇 Fuzzing Rust code with American Fuzzy Lop
vscode-rust
Mockito - HTTP mocking for Rust!
rust.vim - Vim configuration for Rust.
shiny - a shiny test framework for rust
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
rFmt
Rust for Visual Studio Code
cargo-fuzz - Command line helpers for fuzzing
intellij-rust - Rust plugin for the IntelliJ Platform