Here’s a simple example. The variable
x has a list of strings 1, 2, 3
assigned to it. If the array has
parseInt applied to it via
Array.map. What is expected to happen? You would expect that the
strings would be parsed using their base 10 representations. Well that’s
not what happens.
The problem is the callback that
Array.map expects, and how
callback looks like so:
So if I pass in the raw
parseInt function, which takes in 2
parameters the string and an optional radix. The index is received as
the radix to use. So for the 2nd element ‘2’, it sees a 1 radix because
of counting from zero. ‘2’ is not a valid digit in a base 1 system only
proper error. Completely valid decision, just a really irritating one
not to be caught by a linter. It’s a problem with being over-flexible.
It’s just that we were not expecting that. Maybe
parseInt could have
thrown an error when the radix got too big for it to handle, but then
again exceptions really suck.
So the correct way is to curry
parseInt and fill in the 2nd parameter
with what base your strings are in.