Thanks, that actually gave info. It has to be a bug - the constructor that comes up is the Vector2f one but it acts like it's the float one. I'll submit it.
Also, I assumed it was SFML's fault because I've only seen this happen twice before - for FloatRect and IntRect.