new → closed
I can see the utility of
ifNumeric and if we used it in a dozen places like that it would make sense to define it just for the byte savings alone, even if we didn't expose it. But we only have two uses of it, and one doesn't fit that pattern, so I think we might as well stay with what we've already (just) documented and let this be a plugin or external code.
As for the original ticket suggestion, an
isNumeric return value that broke
0 would be a big one in my book. This is a very simple one-line utility function so it's not hard to just ignore
isNumeric and implement one line with whatever semantics you want in your own code. For example, perhaps you really want
isInteger because real numbers and exponentials aren't valid in a particular case.