-
-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement the fast path for list.__getitem__
#119053
Labels
performance
Performance or resource usage
topic-free-threading
type-feature
A feature request or enhancement
Comments
@mpage Can I take a look at this one or you already work on this issue? (I am just asking to avoid the confliction) |
corona10
added a commit
to corona10/cpython
that referenced
this issue
May 17, 2024
corona10
added a commit
to corona10/cpython
that referenced
this issue
May 17, 2024
corona10
added a commit
to corona10/cpython
that referenced
this issue
May 17, 2024
@corona10 - Go for it! |
corona10
added a commit
to corona10/cpython
that referenced
this issue
May 18, 2024
corona10
added a commit
that referenced
this issue
May 21, 2024
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 21, 2024
…gh-119112) (cherry picked from commit ab4263a) Co-authored-by: Donghee Na <donghee.na@python.org>
corona10
added a commit
that referenced
this issue
May 21, 2024
Is there still something to do here? |
No, it's done thanks. |
estyxx
pushed a commit
to estyxx/cpython
that referenced
this issue
Jul 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
performance
Performance or resource usage
topic-free-threading
type-feature
A feature request or enhancement
Feature or enhancement
Proposal:
Implement the fast path for
list.__getitem__
outlined in PEP-703.Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Linked PRs
The text was updated successfully, but these errors were encountered: