Guido van Rossum wrote: > What's exasperating to me about this whole discussion is that nobody has > shown any reason why this kind of code would be occurring in user code. > STORE_FAST x LOAD_FAST x seems that it must come from a user writing > x = x
I think that would be LOAD_FAST(x) STORE_FAST(x). STORE_FAST(x) LOAD_FAST(x) could be caused by something like this: def f(): x = … y = x Presumably this could be replaced with DUP_TOP() STORE_FAST(x)? But I don’t know if that’s any faster. It does require more stack space… > Are we just a solution (a clever peephole > trick) looking for a problem? It seems so. Brandt _______________________________________________ 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/XGFBCVDIEXEBKFGUOHSXJD3GKO7IAYLM/ Code of Conduct: http://python.org/psf/codeofconduct/