scoder

> I would also propose to reshuffle the order of `except +` and `except?`, because AFAICT the `except +` case does not currently do exception checking by default (and assuming...

It is certainly an unfortunate effect on users. We're not the only ones who define cdef functions. Were you referring to „extern” functions? Meaning, real C functions? Those are probably...

> ```python > test.pyx:10:10: Type is not specialized > ``` This is certainly not the best error message ever. We should at least report that no matching signature was found,...

> pointer to function That seems the biggest open question. As soon as we make a distinction between extern and non-extern functions, we end up with the problem that function...

> > And we're still in alpha, so let's use that to gather feedback before the final release. > > ... so why not get it out sooner rather than...

> full CI is skiped for documentation-only changes Yes, that's also a good idea. We'd need a separate documentation build workflow for that, though. Currently, everything is done in the...

> At the time I searched for compiler options to make compilation faster but I couldn't get them to work as easily so I abounded the idea as it wasn't...

> When CYTHON_RUNTESTS_CCACHE is set? I don't think it's used anywhere. The ccache setup for our test runs happens in ci-run,sh.

I fixed some of the Windows failures in master. Only some walrus error tests are still failing now, apparently because of a missing exception message on a SyntaxError.

Ok, so basically, what you do is ```cython cdef char* string = b"xyzabc" print( string[:length].rstrip("abc") ) ``` That could be optimised. It just needs a C function to adapt the...