For internal consistency, to_string() should either list all relevant types (including bool, char, etc.), or only those that are the destination types of integral or floating-point promotion (float not being among them).

A defensible reason for having (or rather keeping) the float overloads anyway could be to exactly mirror the adjacent sets of stoX() function overloads (even without round-trip fidelity for floating-point numbers).

Unfortunately, that reveals a bigger issue than redundant overloads: the glaring and indefensible omission of an overloaded function stoui(). Adding that is not as trivial as removing redundant overloads, of course, because it requires everybody to take action. Still, it is the preferable remedy for the present situation.

As far as I can tell from easily accessible information, C++ has already created the precedent with stoi(), which is not the equivalent of a pair of functions strtoi()/wcstoi() in C, but it would be if such functions existed. The function atoi() may look similar, but it does not qualify because it is as different from a hypothetical strtoi() as atol() currently is from strtol(), with the latter two both Standard C. It is only logical to act on this one-sided precedent by completing the set. Whether or not Standard C leads the way (or follows suit) is immaterial, but an invitation could be extended.