Skip to content

PEP 590: Correct sign of return value of PyVectorcall_NARGS(). #1105

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.

Sign up for GitHub

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

Closed
markshannon wants to merge 1 commit into from
Closed

PEP 590: Correct sign of return value of PyVectorcall_NARGS(). #1105

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pep-0590.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ so it can use this trick at no additional cost.
See [3]_ for an example of how ``PY_VECTORCALL_ARGUMENTS_OFFSET`` is used by a callee to avoid allocation.

For getting the actual number of arguments from the parameter ``n``,
the macro ``PyVectorcall_NARGS(n)`` must be used.
the inline function ``PyVectorcall_NARGS(n)`` must be used.
This allows for future changes or extensions.


Expand All @@ -152,7 +152,7 @@ The following functions or macros are added to the C API:
``*args`` and ``**kwargs`` calling convention.
This is mostly meant to put in the ``tp_call`` slot.

- ``Py_ssize_t PyVectorcall_NARGS(size_t nargs)``: Given a vectorcall ``nargs`` argument,
- ``size_t PyVectorcall_NARGS(size_t nargs)``: Given a vectorcall ``nargs`` argument,
return the actual number of arguments.
Currently equivalent to ``nargs & ~PY_VECTORCALL_ARGUMENTS_OFFSET``.

Expand Down