Eric V. Smith <e...@trueblade.com> added the comment:
I don't want to belabor this, but hey, it's in f-strings! And if it's an actual problem I'd like to fix it. > It can be uninitialized if the parenstack[nested_depth] value is itself > initialized, which can happen if the memory block pointed by parenstack has > not been initialized to some value after malloc'ed and > parenstack[nested_depth] never got a value. parenstack is allocated on the stack, not that that changes the discussion much. It looks like everywhere that parenstack[nested_depth] is read, it's already been written to. Anyway, (if I'm right,) this makes my points that a) there are false positives, and b) we should have separate issues for each actual problem. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46280> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
