Rule to detect changes to iterable object of loop

[mimre25]

Rule to detect changes to iterable object of loop

[mimre25]

Ok, I was seeing something, but that code wasn't used - I've opened #488 to remove it, to avoid future bugs 🙂

[cooperlees]

This is released and we have dedicated improvements issue. So let's move there.

I yanked 24.1.15 + 24.1.15 due to bugs.

[cooperlees]

Yeah, I think we've all been here.

This sounds good, but I think in general we should just detect if it is a mutable iterable when we see remove in a loop and suggest saving the indexs and then removing them in reverse? Or am I missing something here?

Anyways, in general this sounds good. Feel free to make a POC diff and we can comment on there.

[mimre25]

I've went with an approach that alerts for any mutations of the loop iterator (eg .remove or del).

PR is in #446

[mimre25]

FYI: While starting to implement this rule into ruff yesterday I might have found a bug in my initial implementation.

@cooperlees please hold off the release until I verify my suspicion and fix it ~ I'll check this out later today.