| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
This seems like an okay workaround , but I think the underlying problems is that we really shouldn't be including headers under an extern "C". I've raised this issue before: It can (and has) caused problems with system headers too. |
Sorry, something went wrong.
There was a problem hiding this comment.
Nice workaround.
I tried modifying the 123 header files in Include/internal/ to move #include outside extern "C" { ... }. It's a lot of work, it will be hard to maintain in the future, I don't think that it's worth it.
Sorry, something went wrong.
|
What's the status here? This would also resolve one of the remaining issues with making mypyc compatible with 3.13. Would be great if it could be included in 3.13.0rc2. #121489 (comment) |
Sorry, something went wrong.
|
Thanks @mdboom for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
|
GH-123035 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The vendored mimalloc headers are designed to be used in a C++ context if imported from C++. Therefore, we should switch the context back to C++ when using a C++ compiler here. This seems like the most future-proof fix, because otherwise we would need to be careful what context we import pycore_mimalloc.h from.