[Python-Dev] PEP 575 (Unifying function/method classes) update (original) (raw)
Jeroen Demeyer J.Demeyer at UGent.be
Sun Jun 17 13:07:34 EDT 2018
- Previous message (by thread): [Python-Dev] PEP 575 (Unifying function/method classes) update
- Next message (by thread): [Python-Dev] PEP 575 (Unifying function/method classes) update
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2018-06-17 14:50, Ronald Oussoren wrote:
This looks interesting. Why did you add a tpccalloffset slot to the type with the actual information in instances instead of storing the information in a slot?
Think of built-in functions. Every built-in function is a different callable and calls a different C function. So it must be stored in the instances.
However, the case where all instances share a PyCCallDef is also possible: all instances would then simply have the same PyCCallDef pointer.
Jeroen.
- Previous message (by thread): [Python-Dev] PEP 575 (Unifying function/method classes) update
- Next message (by thread): [Python-Dev] PEP 575 (Unifying function/method classes) update
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]