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 | benjamin.peterson |
|---|---|
| Recipients | Aaron Hall, benjamin.peterson, mark.dickinson, serhiy.storchaka, thatiparthy, vstinner |
| Date | 2018年10月26日.06:00:42 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1540533642.85.0.788709270274.issue35059@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Why do we need this Py_STATIC_INLINE macro? If you want to have one for enabling always inline, that's fine with me, since it's compiler-specific. But the current Py_STATIC_INLINE macro seems to conflate linkage with always-inline behavior. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018年10月26日 06:00:42 | benjamin.peterson | set | recipients: + benjamin.peterson, mark.dickinson, vstinner, serhiy.storchaka, thatiparthy, Aaron Hall |
| 2018年10月26日 06:00:42 | benjamin.peterson | set | messageid: <1540533642.85.0.788709270274.issue35059@psf.upfronthosting.co.za> |
| 2018年10月26日 06:00:42 | benjamin.peterson | link | issue35059 messages |
| 2018年10月26日 06:00:42 | benjamin.peterson | create | |