I noticed thatmove_toward is not grammatically correct, but I think some other people will have a better name thanmove_towards, so I'll leave it for now until there are some better name suggestions.

Alright, I'm done with themove_towards().
I did some performance testing with the Python version.

importpygameimporttimestart=time.perf_counter()defvector2_move_towards(origin,target,speed:float):"""Moves towards the target Vector2 by the movement speed.    Must be put in a loop until its reached its target.    Parameters:        origin: The original position        target: The target position.        speed: The movement speed.    """delta=target-origindist=delta.magnitude()if (dist<=speedordist==0):returntargetreturnorigin+delta/dist*speedvec1=pygame.Vector2(10,20)vec2=pygame.Vector2(30,30)speed=1vec3=vector2_move_towards(vec1,vec2,speed)print(vec3)end=time.perf_counter()print(end-start)

Here are the results:

C:0.00005339999Python:0.00011449999874457717

Time to work onmove_towards_ip()!

Edit: It looks like after I gotmove_towards() working,move_towards_ip started working... lol.

This also needs unittests and type stubs

Done!

Lots of changes 😅

Whoops, looks like I rushed things lol.

There's a problem with input parsing

>>>a=pygame.math.Vector2((0,0))>>>a.move_towards((10,10),2)<Vector2(1.41421,1.41421)>>>>b=pygame.math.Vector3(0)>>>b<Vector3(0,0,0)>>>>b.move_towards(a,2)<Vector3(0,0,1.42421e-306)>>>>a.move_towards((1,2,3,4,5,6,7,8),10)Traceback (mostrecentcalllast):File"<stdin>",line1,in<module>TypeError:ExpectedVectorasargument1

If the dimensions aren't equal, it should fail, presumably

And if the input is rejected, it shouldn't say it expected a Vector, since it can take vector-like. Pygame rect functions would call this "Rect-style," so that could be used here as "Vector2-style" or "Vector3-style"

Also I'm putting in a commit that fixes a couple things with the example.
It adds it to the examples listing, and it makes it a size that will work on people's 125% scaled displays (like mine), and it does pygame.quit() properly.

I left some suggestions. No need to change them in this PR or at all. Approving anyway.

Thanks! I'll be looking to resolving these later today.

As of 2023 it works perfectly and never gives any problem. Good job guys.