You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've looked into using Numpy vectors instead of the Pos class.
Would need to extensively refactor Drawing and originalDrawingMethods
A lot of the vector arithmetic would simplify if using a Numpy vector, however we'd have to wrap the Numpy vectors to use in the Drawing, to add the relevant methods needed, and the wrapping class would end up looking a lot like Pos. I think this issue is not quite worth doing (yet)
One improvement could be in Pos to store the coordinate internally as a Numpy vector, instead of self.x, self.y
I'll leave the issue open, but put to the bottom of the list for now.
See related ticket #28 which does the same for Vector2D, Matrix2D which are used by the Fractal classes
The text was updated successfully, but these errors were encountered: