[BUG] Segmentation fault with Walrus-Operator and same named variables about cython HOT 2 OPEN

Thanks - in the short term I suspect the better solution is to treat assignment expressions as "maybe assignments" rather than "definite assignments". There's quite a few variations of cases like this where it isn't clear if they're actually run and which our flow control doesn't currently cover so working it out comprehensively is likely hard.

That'll de-optimize assignment expressions slightly but I think that's OK.

from cython.

walrus define variable after or operate, make gunicorn crash: [ERROR] Worker (pid:9467) was sent code 139!

def func(cell: dict):
    if (flag := True) or ((text := cell.get("text")) and text.isdigit()):
        return True
    text = cell.get("text") or cell.get("value")
    return text

Expected: raise some error at lease

from cython.