ruff-ecosystem results

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

Yep, makes sense! I was a bit disappointed to see an empty ecosystem report again.

Claude unfortunately hasn't been too helpful yet, but I'll keep thinking about it. I think we're looking for cases that are still Calls or Subscripts but with bodies that cause needs_parentheses to return either Always or Multiline since those are the only cases that now take precedence over the old Call | Subscript check.

I pushed a couple of somewhat tricky cases for other expression types inside of calls, but these are handled fine on main. After looking through the branches in needs_parentheses, I think I'm fully convinced that the only special cases are implicitly concatenated strings and fluent call chains, both of which are handled correctly now (fluent call chains were handled properly before, and now the special case is generalized). Other expression types already require their own parentheses when they're the target of a call or subscript and thus aren't affected by this bug.

Sounds good. Thanks for taking the time to assess the impact of this change.

An example like this (specifically testing the different break points) might be good to verify:

foo = lambda: call()(extra_argument_one, extra_argument_two, extra_argument_three)