Should we be ignoring all dunders?

We have an is_known_dunder_method method that we could use for that.

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

@charliermarsh I updated using is_known_dunder_method (this required making crate::rules::flake8_boolean_trap::helpers public).

However, I am not sure if this is the best approach. For one, there is no official list of dunder methods from python's side, and what is considered a known dunder method can change from one version to the next.

Maybe a simpler approach would be to just exclude dunder methods in general? This would be easier to document/teach as well.

The is_known_dunder_method also contains __init__ and __new__, which are probably the two most important functions for FBT001 to check.

I think "all dunder methods except init and new" should be easy to maintain and explain.