-
-
Notifications
You must be signed in to change notification settings - Fork 18k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use fused types to avoid tempita #22411
Comments
Would be interested in seeing how this works - the templating system is sparsely documented so I'd definitely be +1 if there is a viable alternative |
tried this a while back personally i don’t think this makes it more readable because of the special cases for object but certainly give a try note we for example already have numeric fused types |
OK, I'll poke at this after #22329, #22287, #22283 go through; any earlier and I'd be swimming in merge conflicts.
It may turn out that way in the end; my intuition is that the learning curve for someone not familiar with tempita will make a pretty big difference. |
If there were no special cases, I would prefer fused types over |
AFAICT this process has gone as far as it can go. Closing. |
ok! |
A lot of the cython code is templated to avoid duplication, but is not especially readable (see anything in _libs with filename ending in ".pxi.in").
AFAICT we can use fused types and cython will internally generate all of the relevant functions. If this understanding is correct, the code can be made a lot friendlier.
The text was updated successfully, but these errors were encountered: