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.
Should we encourage/document `lru_cache` as the way to do `call_once`? If so,
then I guess that’s suitable, but people ha
> Why not? It's a decorator, isn't it? Just make it check for number of
> arguments at decoration time and return a different object.
It’s not that it’s impossible, but I didn’t think the current implementation
doesn’t make it easy
(https://github.com/python/cpython/blob/cecf049673da6a24435acd1
