Alberto
Alberto
Oh ok so what you really wanted was checking for collision, kinda like Line.colliderect(). Luckily, that's coming in the geometry module with the Line class.
> @itzpr3d4t0r that recent commit confuses me in context of all the rest of the changes here. Am I missing something, or is this incomplete for now? You can shallow...
I think we could remake our SIMD backend to be more similar to SDL's, where they compile/include all symbols in a single header file: [SDL_intrin.txt](https://github.com/user-attachments/files/15986234/SDL_intrin.txt) Like the bulk of the...
Didn't see that coming but it doesn't allow you to change more than one color per call (which tbh is a more realistic usecase), that means that it will run...
Needless to say I'm on the same boat with @Damus666 on this one. I think this move makes sense and it's actually an elegant solution which requires minimal code change...
Yeah an actual reproducible program and results would make things easier.
This optimization effort is truly impressive and worth celebrating. However, the number of changes and the effort needed to review them make it quite challenging. Since these are mostly macro...
Yep but this is way faster than that. It would also allow us to reuse this kwarg in Circle/Line and Polygon in the future to avoid having to implement the...
This sounds pretty useful, sign me up!
PS. This is based on test I made with a tentative implementation, These are the results:  ``` === blit_colorkey === Total: 239.3913035001351 Mean: 0.004776 Median: 0.003755 Stdev: 0.004270 ===...