On 4/29/2020 3:55 AM, Tom Forbes wrote:
Hey Raymond, Thanks for your input here! A new method wouldn’t be worth adding purely for performance reasons then, but there is still an issue around semantics and locking.
One thing I don't understand about the proposed @call_once (or whatever it's called): why is locking a concern here any more than it's a concern for @lru_cache? Is there something special about it? Or, if locking is a requirement for @call_once (maybe optionally), then wouldn't adding the same support to @lru_cache make sense?
Eric _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/SKYGVHA3BHZSQC6VFSQOE2D6GJQGEDMD/ Code of Conduct: http://python.org/psf/codeofconduct/
