mut_range_bound check for immediate break after mutation

[dswij]

closes #7532

mut_range_bound ignores mutation on range bounds that is placed immediately before break. Still warns if the break is not always reachable.

changelog: [mut_range_bound] ignore range bound mutations before immediate break

[rust-highfive]

r? @flip1995

(rust-highfive has picked a reviewer for you, use r? to override)

[bors]

☔ The latest upstream changes (presumably #7604) made this pull request unmergeable. Please resolve the merge conflicts.

[flip1995]

LGTM now. All comments are about technical debt with this lint, which you uncovered by working on this lint 😛

[flip1995]

Last comment. Thank for addressing all of my complaints 😄

[flip1995]

Suggested change

	/// False positive when mutation is not immediately followed by a break statement
	/// False positive on nested expressions ([#6072](https://github.com/rust-lang/rust-clippy/issues/6072))
	/// False positive when mutation is followed by a `break`, but the `break` is not immediately after the mutation:
	///
	/// ```
	/// x += 1; // x is range bound
	/// some_other_expr();
	/// break; // leaves the loop so mutating is not an issue
	/// ```
	///
	/// False positive on nested loops ([#6072](https://github.com/rust-lang/rust-clippy/issues/6072))

[flip1995]

@bors r+

Thanks!

[bors]

📌 Commit dc6f7dc has been approved by flip1995

[bors]

⌛ Testing commit dc6f7dc with merge f356784...

[bors]

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: flip1995
Pushing f356784 to master...