Make each assignment to define a distinct variable with independent type

首先阅读相关 issue #6233 和 #6232，然后查看 issue 中提到的原型实现。拟议的工作是使用不同的内部变量和 phi 节点进行通用变量重命名遍历，并以兼容当前语义为完成目标。

These long-standing issues can be solved by generalizing the variable renaming pass that is used by --allow-redefinition:

• #6233
• #6232

Each assignment to a name would generate a separate internal variable. We will use "phi nodes" to merge these variables when different control flow paths assign to different variants. Here is a simple example:

def f() -> None:
    if c():
        x = 0
    else:
        x = ""
    reveal_type(x)

The new variable renaming pass would produce a new AST that resembles this program (note that phi(...) is a new special AST node type and not a function call):

def f() -> None:
    if c():
        x = 0
    else:
        x' = ""
    x'' = phi(x, x')
    reveal_type(x'')  # int | str

This resembles the static single assignment form (SSA) used by many compilers, but probably would not conform to it 100% due to various practical reasons.

I'm working on a prototype implementation.

I hope that we can make this sufficiently compatible with the current semantics so that we can enable it by default (in mypy 2.0, possibly).

An alternative way to provide similar functionality would be to infer variable types from multiple assignments, similar to what already happens if a variable is declared as x: object. The renaming approach has a few notable benefits:

• It can (more) easily support partial types (e.g. inferring a list item type from an x.append call).
• It's a generalization of how we've already implemented --allow-redefinition.
• It should make it easier to generate efficient code in mypyc.
• The implementation will mostly be a new renaming pass, so it won't make other parts of mypy much more complicated (though mypyc needs changes).
• The conditional type binder has some tech debt and I'm not excited about making it even more complicated, which would be the case if we'd use the alternative approach.