iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 670: remove duplicated paragraph (#2118)

This commit is contained in:
Victor Stinner 2021-10-20 01:47:53 +02:00 committed by GitHub
parent 157ab6ee10
commit ccb8ee3cc3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
pep-0670.rst
View File

@ -123,19 +123,6 @@ especially useful on LTO+PGO builds which heavily inlines code: see
``__declspec(noinline)`` with MSC.
Convert macros and static inline functions to regular functions
---------------------------------------------------------------
There are projects embedding Python or using Python which cannot use
macros and static inline functions. For example, projects using
programming languages other than C and C++. There are also projects
written in C which make the deliberate choice of only getting
``libpython`` symbols (functions and variables).
Converting macros and static inline functions to regular functions make
these functions accessible to these projects.
Specification
=============
@ -158,12 +145,17 @@ The following macros should not be converted:
Convert static inline functions to regular functions
----------------------------------------------------
Converting static inline functions to regular functions give access to
these functions for projects which cannot use macros and static inline
functions.
There are projects embedding Python or using Python which cannot use
macros and static inline functions. For example, projects using
programming languages other than C and C++. There are also projects
written in C which make the deliberate choice of only getting
``libpython`` symbols (functions and variables).
Converting static inline functions to regular functions makes these
regular functions accessible to these projects.
The performance impact of such conversion should be measured with
benchmarks. If there is a significant slowdown, there should be a good
benchmarks. If there is a significant slowdown, there should be a good
reason to do the conversion. One reason can be hiding implementation
details.