Author eric.smith
Recipients eric.smith, nanjekyejoannah, pablogsal, rhettinger, zach.ware
Date 2022-01-06.19:36:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1641497812.1.0.00056280147566.issue46280@roundup.psfhosted.org>
In-reply-to
Content
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.
History
Date User Action Args
2022-01-06 19:36:52eric.smithsetrecipients: + eric.smith, rhettinger, zach.ware, pablogsal, nanjekyejoannah
2022-01-06 19:36:52eric.smithsetmessageid: <1641497812.1.0.00056280147566.issue46280@roundup.psfhosted.org>
2022-01-06 19:36:52eric.smithlinkissue46280 messages
2022-01-06 19:36:52eric.smithcreate