> I wonder how this caching works, given that the dynamic nature means
> that virtually every operation could have side effects, causing wrong
> behaviour when cached. The only mitigation for this that I can imagine
> is that caching just occurs for basic operations defined in the standard
>
The CACHE opcode is a new 3.11+ opcode which is kind of a NOP but is used by
some other opcodes to store cache information for specialization. A map of
-> is in `dis._inline_cache_entries`
if that helps with this.
___
Python-Dev mailing list --
