unnecessary-literal-set (C405): also warn about `set({})`
Open
rule
- Dominant language
- Rust
- Stars
- 49.6k
- Forks
- 2.4k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 435
Description
### Summary
I have seen this a few times. It would be nice if [C405](https://docs.astral.sh/ruff/rules/unnecessary-literal-set/) would warn about this case as well. `{...}` is a literal set so seems reasonable to warn about `{}` in addition to `[]`.
Contributor guide
Research direction
Start with the linked C405 rule documentation and locate the rule's implementation and tests. Compare the existing handling of the [] case with the requested {} case; done means C405 also warns about set({}) consistently with literal-set handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100