Skip to content

Conversation

@jdemeyer
Copy link
Contributor

@jdemeyer jdemeyer commented May 20, 2019

@encukou
Copy link
Member

encukou commented May 31, 2019

I'll work on updating the docs today.
@jdemeyer I'll push changes your branch directly, if you don't mind.

@encukou
Copy link
Member

encukou commented May 31, 2019

Rebased & updated

encukou added 2 commits June 3, 2019 00:12
This is not described in detail in PEP 590;
see python#13699
for the practical issue.
@encukou encukou marked this pull request as ready for review June 2, 2019 22:23
@encukou encukou merged commit 9e3e06e into python:master Jun 2, 2019
@jdemeyer
Copy link
Contributor Author

jdemeyer commented Jun 3, 2019

In Doc/c-api/structures.rst, I planned to give a high-level explanation of the vectorcall protocol (basically a short version of PEP 590). Right now this is not really explained. That's why I defined vectorcallfunc there.

Do you still think that this is a good idea?

@encukou
Copy link
Member

encukou commented Jun 3, 2019

I don't think c-api/structures is a good place, since vectorcall is not a structure.
But perhaps a new chapter on calling under "Abstract Objects Layer" would make sense – calling takes up half of c-api/object already.

DinoV pushed a commit to DinoV/cpython that referenced this pull request Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants