Micha Reiser

You can follow our work on red-knot (see the `red_knot` crate and issues/PRs labeled with `red-knot`)

This is happening right now but we decided to build it outside ruff first because it's a pretty big architectural shift. See [astral-sh/ty](https://github.com/astral-sh/ty?rgh-link-date=2025-05-09T19%3A04%3A54.000Z)

Hi @LordAro I'm struggling to understand how your question relates to `C409` because the rule doesn't trigger for me with the given code example (see [this playground](https://play.ruff.rs/199728fc-7494-435e-8f0d-a8bf894b90db)). However, your example...

Thanks for updating the issue. Glad to hear that we're talking about the same :) I agree, `()` is very unambiguous. I can see how `(foo,)` is harder to spot....

> 2. Another helpful rule is to detect declarations in __all__ that are unused This would require multifile analysis, which Ruff doesn't support today. Even then, the rule would be...

@gpauloski I could see such a rule to be useful, but we should think about its scope. E.g what about empty `else` branches (in `for`, `try` etc statements)? And we...

Yeah, this requires pre-commit support and possibly support for passing multiple ranges https://github.com/astral-sh/ruff/issues/12800