Enforce `x`, `x1`,` x2` naming consistency

Rule request

Thesis

I often see that some people use this naming pattern:

x1 = 1
x2 = 2

Which is perfectly fine. But, this one looks ugly:

x = 1
x2 = 2

Note x1 vs x2 difference.

Reasoning

My proposed solution is to create a new naming rule to check that if a variable named something1 or something2 there should not be just something in the current scope. While just something and something1 with something2 are totally fine.

Our own code will have lots of these issues!

[Dreamsorcerer]

Might also want to consider checking for underscores:

x = 1
x_2 = 2

[sobolevn]

Ok, this is hard. There are lots of corner cases and small things to think about.

For example, attributes need special handling:

• some.x and some.x2 are violating this rule
• while some.x and other.x2 are not

So, I am moving this feature for the next version.