René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"PEP 670: Convert static inline functions to functions","articleBody":"[PEP 670](https://peps.python.org/pep-0670/) converted macros to static inline functions in Python 3.11. I propose to implement the second phase of PEP 670: convert static inline functions to regular functions in Python 3.12.\r\n\r\nStatic inline functions are causing C++ warnings. I had to add _Py_CAST() and _Py_NULL macros to Python 3.11 to limit the number of C++ warnings. The _Py_CAST() macro has a complicated history. @serge-sans-paille helped me to write a correct C++ implementation of _Py_CAST(), but it had to be reverted to fix the issue #94731. See:\r\n\r\n* https://github.com/python/cpython/pull/94782\r\n* https://github.com/python/cpython/pull/32175#issuecomment-1181938543\r\n* https://github.com/python/cpython/pull/94782\r\n\r\n[As explained in PEP 670](https://peps.python.org/pep-0670/#convert-static-inline-functions-to-regular-functions), static inline functions cannot be used in programming languages other than C, and these functions cannot be loaded by loading the symbol from the Python library (libpython). For example, the vim text editor loads uses the Python C API by loading symbols.\r\n\r\nConverting static inline functions also hides implementation details. When using regular function calls, at the ABI level, it's just a regular function call, the machine code doesn't access directly structure members. So we have more freedom to changes Python internals (like the structure).\r\n\r\nThis issue is not about changing Python internals. It's just about convert static inline functions to regular functions.","author":{"url":"https://github.com/vstinner","@type":"Person","name":"vstinner"},"datePublished":"2022-09-22T15:41:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/97016/cpython/issues/97016"}