If you think the previous issue was closed prematurely then you can leave a comment there asking for it to be re-opened.
Please take a look at other issues on the bug tracker to get an idea of what's in and out of scope. We don't generally allow issues like "micro-optimise this entire module" - they're too broad and not useful enough to other developers.
Activity
barneygale commented on Apr 8, 2024
Duplicate of #117349, please don't do this. The bug tracker is not your personal to-do list.
nineteendo commented on Apr 8, 2024
Must I link to the closed issue then? This PR is about further changes.
barneygale commented on Apr 8, 2024
If you think the previous issue was closed prematurely then you can leave a comment there asking for it to be re-opened.
Please take a look at other issues on the bug tracker to get an idea of what's in and out of scope. We don't generally allow issues like "micro-optimise this entire module" - they're too broad and not useful enough to other developers.
nineteendo commented on Apr 8, 2024
Not prematurely, I just found new optimisations.
There is a particularly inefficient loop in ntpath: #117610 (comment)
Can I add some other optimisations alongside it?