On Thu, 12 Mar 2020 at 19:52, Andrew Barnert <[email protected]> wrote: > I suppose it could track calls out to C functions as they happen and mark > every value that was live before the call, and then instead of numpy checking > refs==1 is could check refs==1 && !c_flagged, and then it wouldn’t need the C > frame hackery. But that seems like it would slow down everything in exchange > for occasionally helping numpy and a few other C extension libs.
The author of the patch says this is already implemented in string concatenation in Python itself. Maybe we should look at the implementation, but I don't know where and what to search. _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/K77CRMC3VWQH56RVSZCS3JYUSRS6QOLE/ Code of Conduct: http://python.org/psf/codeofconduct/
