| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| Use 2 bytes for each instruction. Previously the number of bytes varied | ||
| by instruction. | ||
|
|
||
| .. versionchanged:: 3.11 |
There was a problem hiding this comment.
Maybe don't document this until we are sure it's what we want?
Sorry, something went wrong.
There was a problem hiding this comment.
I'd prefer to keep it, and change it if/when dis changes (which is easy enough). That way we don't forget to document it.
Sorry, something went wrong.
There was a problem hiding this comment.
OK. Once we've started doing this we will need to complete it before the beta release anyway.
Sorry, something went wrong.
|
Looks good in general. |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @brandtbucher for commit 1aa079c 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
Sorry, something went wrong.
|
👍 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Here's a sort-of-rough first pass at implementing this idea. BINARY_OP is easy to start with, since it only uses its cache for the adaptive counter member. Initial perf testing doesn't show any impact, which I think is good (it means that the basic idea works well, even when the cache isn't being used).
Related changes:
https://bugs.python.org/issue46841