scoder
Friendly ping @mhils :)
Closes https://github.com/cython/cython/issues/6164
> Another approach would be to turn on `CYTHON_USE_TYPE_SPECS` on all implementation and deprecate all this ... Type specs mean that we end up with heap types everywhere. That's not...
> This requires C99 compliant compilers Given that Cython 3.1 is the release where we cut off old tails, I suggest that we also wait with this until then. I...
>> Designated initializers require c++20 > > I see them in CPython v3.6.0 (released in 2016) but I could not find use > of them in 2.7.18 (released 2020). CPython...
Would be nice to have this updated. I'd like to have this integrated into Cython 3.1.
Thanks for the update. Sadly, we cannot require C++20 any time soon, so we'll have to postpone this, which probably means that it will bit rot away under our feet....
I've split the feature flags at need more than once. This seems reasonable. Something like "avoid long borrowed refs" or "avoid unique borrowed refs" might catch the idea of not...
> The reason for this difference is that Cython is being run from the build directory Is there a reason why Cython cannot run from the main project directory here?...
> relative paths are better especially for paths that end up in the final extensions modules … or in the distributed sources. One reason why Cython tries to avoid absolute...