Browse Source
bpo-37207: Use vectorcall for range() (GH-18464)
bpo-37207: Use vectorcall for range() (GH-18464)
This continues the `range()` part of #13930. The complete pull request is stalled on discussions around dicts, but `range()` should not be controversial. (And I plan to open PRs for other parts if this is merged.) On top of Mark's change, I unified `range_new` and `range_vectorcall`, which had a lot of duplicate code. https://bugs.python.org/issue37207pull/18553/head
committed by
GitHub
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 35 additions and 17 deletions
-
2Misc/NEWS.d/next/Core and Builtins/2019-06-09-10-54-31.bpo-37207.bLjgLR.rst
-
50Objects/rangeobject.c
@ -0,0 +1,2 @@ |
|||
Speed up calls to ``range()`` by about 30%, by using the |
|||
PEP 590 ``vectorcall`` calling convention. Patch by Mark Shannon. |
|||
Write
Preview
Loading…
Cancel
Save
Reference in new issue