> Indeed, internally it rewrites the AST, of course. I think that's the
> simplest way to implement it. But it doesn't mean the user that write
> the compile-time code would have to be aware of the AST at all.
> I mean, if you have a good use-case for it, then I'm ok with allowing
> the compile-tim
Prakhar Goel,
> Doesn't this just punt on how CdefFunction works? Feels like we're
> back to AST re-writing.
Indeed, internally it rewrites the AST, of course. I think that's the
simplest way to implement it. But it doesn't mean the user that write
the compile-time code would have to be aware of t
Greg,
I assume the ast returned by twice will have the AST from f embedded in
there somehow so no closure required.
Something like:
cdef _tmp_foo(...):
# same as foo...
cdef foo(...):
_tmp_foo()
_tmp_foo()
-- PG
___
cython-devel mailing l
Hi.
I would like to start contributing in a meaningful way to Cython on the
order of ~1 day a week, within the framework of the time allocated to me
from my employer (Quansight Labs) toward open source contributions. Over
time, my goal is push for an HPy[0] backend for Cython, but I also want
