{{ message }}
bpo-35059: Remove Py_STATIC_INLINE() macro#10216
Merged
vstinner merged 1 commit intoOct 29, 2018
Merged
Conversation
Member
Sorry, something went wrong.
"static inline" should be used directly. Forcing the compiler to inline is not recommended.
Member
Author
|
See https://bugs.python.org/issue35059 for the rationale. |
Sorry, something went wrong.
|
Hi! The buildbot AMD64 FreeBSD CURRENT Shared 3.x has failed when building commit 542497a. You can take a look here: |
Sorry, something went wrong.
Member
Author
|
"ERROR: test_start_tls_server_1 (test.test_asyncio.test_sslproto.SelectorStartTLSTests)" is known issue: https://bugs.python.org/issue35045 |
Sorry, something went wrong.
Member
Author
|
Sorry, the correct link is: https://bugs.python.org/issue35031 |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.
"static inline" should be used directly. Forcing the compiler to
inline is not recommended.
https://bugs.python.org/issue35059