scoder
scoder
Maybe we could apply this only to memory views in variables with a single assignment? I.e. arguments and stuff that is set up "earlier" (usually at the beginning of the...
Are we still pursuing this, or can the PR be closed?
> is the issue still open ?. If its still open can you please assign it to me Feel free to send a PR.
I just noticed one issue with this approach. When new builtins are added and users refer to them in their code, we will generate code to look them up at...
> I added the `builtins` set in `Builtin.py` as recommended, but this creates a circular import, so I let the list of class names in `Symtab.py`. Given that the `uncachable_builtins`...
Closed by https://github.com/cython/cython/pull/6043/ I moved the actual set from Symtab.py into Code.py in https://github.com/cython/cython/commit/4bc10b9f41c29cfc8c093b6d7c2505894c6e40ca
Isn't the constant result calculated already at this point?
If the numpy header doesn't do anything special on top of `libc.math`, then I'd first migrate all declarations in `numpy/math.pxd` to use libc's `math.h` instead, except for the few that...
Thanks for the ping. Definitely something to discuss for Cython 3.0 again.
Good question. :) Let me collect a couple of thoughts on this. First of all, regarding the examples at hand, the obvious solution for users is to not use `PyList_SetItem(lst,...