-
Separate from #389, the warnings when running `cargo doc -p masonry` need to be fixed.
Most of them are about things that no longer exist within masonry or have perhaps changed names, so it should …
-
Given how our codebase has grown, it no longer makes sense to run clippy on each individual package. We should instead have one check that runs `cargo clippy --workspace -- -D warnings` (and similar f…
-
# What it does
Checks for function arguments having the similar names differing by an underscore.
# Why is this bad?
It affects code readability.
# Example
```rs
fn foo(a: i32, _a: i32…
-
## Reproduction
Here is sample well-formed code that shouldn't trigger clippy lints:
```rust
#[async_trait::async_trait]
pub trait Foo {
#[tracing::instrument(err)]
async fn bar() -> R…
-
Before committing is very useful to always have fmt and clippy executed so we avoid to have the git log full of fmt and clippy and git blame is more likely to point to the right commit.
-
# What it does
Checks for unnecessary double parentheses.
# Why is this bad?
This makes code harder to read and might indicate a mistake.
# Example
```rs
fn simple_double_parens() -> i…
-
**Describe the bug**
When using `#[derive(Reflect)]` inside a workspace where the [`clippy::wildcard_imports` lint](https://rust-lang.github.io/rust-clippy/master/index.html#/wildcard_imports) is dis…
-
# What?
Use clippy and enforce via CI.
# Why?
Clippy is a great lenting tool which enforces good and consistent programming standards.
# How?
+ Use clippy locally.
+ Use clippy in CI and enforce cli…
-
# What it does
Checks for erasing operations, e.g., x * 0.
# Why is this bad?
The whole expression can be replaced by zero. This is most likely not the intended outcome and should probably be…
-
# What it does
Checks for equal operands to comparison, logical and bitwise, difference and division binary operators (`==`, `>`, etc., `&&`, `||`, `&`, `|`, `^`, `-` and `/`).
# Why is this bad…