Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.7k
gh-100110: Specialize FOR_ITER for tuples#100109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
netlifybot commentedDec 8, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
✅ Deploy Preview forpython-cpython-preview canceled.
|
markshannon commentedDec 8, 2022
I'm not sure that I entirely trust those stats, yet. |
markshannon left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Looks good.
Have you attempted to benchmark this?
Fidget-Spinner commentedDec 8, 2022
No. It's just one specialisation. I doubt anything in pyperformance will change. |
markshannon commentedDec 8, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I'm running the stats on it. |
markshannon commentedDec 9, 2022
Thestats show what I would expect. No specialization failures for tuples, and an increase of hit rates for |
Uh oh!
There was an error while loading.Please reload this page.
Same as FOR_ITER_LIST, but it accounts for 57% of our current failures.
https://github.com/faster-cpython/ideas/blob/main/stats/pystats-python-a87c46e-2022-12-04.md#specialization-attempts-3