-
`#[allow(bevy::main_return_without_appexit)]`, `-A bevy::main_return_without_appexit`, and adding `main_return_without_appexit = "allow"` to `Cargo.toml` all fail.
![image](https://github.com/user-…
BD103 updated
19 hours ago
-
Hey all.
As we wrap up analyzer support for wildcards, we've got some open questions about how we want the linter to behave to support (and nudge folks towards idiomatic use of) wildcards. What opi…
-
Accommodating wildcards implies changes to a number of existing diagnostics and lints. In a number of places we're already supporting a kind of simulation of wildcards (ignoring unused catch parameter…
-
Problem:
I am encountering a dependency conflict between the odoo_rpc package and the flutter_lints package in my Flutter project. When trying to use the latest version of odoo_rpc (version 0.5.4) al…
-
It would be nice to improve our workflow with a stricter set of linting rules. We are currently using the Dart recommended rules plus:
- avoid_print
- prefer_const_constructors
- prefer_const_const…
-
There are various "patterns" we don't want in the compiler out of one reason or another. I'm using this issue to collect them and create lints for detecting those patterns. The lints will only be avai…
-
Sometimes I want to ignore lints but I don't know what is the lint name. So I git `alt`+`Enter` and I don't get any suggestions for ignoring the lint. It would be useful that all lints generating warn…
-
We should add a standardized set of rustc lints and clippy lints to all our projects. If we raise MSRV to 1.74, we can add them directly to `Cargo.toml`.
See [zulip discussion](https://xi.zulipchat…
-
Write a Bash script that automatically extracts documentation from the docstrings of the lints, creating Markdown files to publish in the detectors' documentation.
-
We should take advantage of the recent Cargo support for workspace lints so we have consistency across all packages.