This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients nascheme, serhiy.storchaka, steve.dower, vstinner
Date 2020-02-08.12:08:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1581163724.6.0.326604782021.issue39573@roundup.psfhosted.org>
In-reply-to
Content
"static inline" functions are not opaque - as they get inlined into 3rd-party compiled code, we can't change anything they reference, and so the structure layout is still fixed and has to be visible to the user's compiler.

I'm not totally against the changes, but it's worth pointing out that you aren't achieving what the issue title claims, so it's really just code cleanliness (and/or introducing macro-users to static inline functions ;) ).
History
Date User Action Args
2020-02-08 12:08:44steve.dowersetrecipients: + steve.dower, nascheme, vstinner, serhiy.storchaka
2020-02-08 12:08:44steve.dowersetmessageid: <1581163724.6.0.326604782021.issue39573@roundup.psfhosted.org>
2020-02-08 12:08:44steve.dowerlinkissue39573 messages
2020-02-08 12:08:44steve.dowercreate