parseInt() takes to arguments, a string and a radix. I usually pass just the string I want converting as a number, you are passing both the string and the radix!
map gives us the value and the index (and the actual array)
map calls a provided callback function once for each element in an array, in order, and constructs a new array from the results. callback is invoked with three arguments: the value of the element, the index of the element, and the Array object being traversed.
take a list of strings that represent numbers and return a new list with all the strings converted to the numbers they represent, but they now have the data type of number
if you execute this statement, the result will be [10, NaN, 2, 3]. Why?
But if you use parseFloat instead of parseInt, you will get the list of numbers.
I can't really explain why this is happening. But you can use this one as a replacement:
Top comments (6)
parseInt()takes to arguments, astringand aradix. I usually pass just the string I want converting as a number, you are passing both the string and the radix!mapgives us the value and the index (and the actual array)By just doing
.map(parseInt)parseIntis taking both the value and the index.Basically the second iteration is
parseInt('10',1)and returnsNaN.Finally, to test that that's what happens, the following would return
"0: 10" "1: 10" "2: 10" "3: 10"This is because from Array.prototype.map
Also from parseInt()
So when this is executing it will return
take a list of strings that represent numbers and return a new list with all the strings converted to the numbers they represent, but they now have the data type of number
if you execute this statement, the result will be [10, NaN, 2, 3]. Why?
But if you use parseFloat instead of parseInt, you will get the list of numbers.
I can't really explain why this is happening. But you can use this one as a replacement:
whoa, you're right. Can someone explain what is happening?
I usually write map functions like this
and that does indeed return [10, 10, 10, 10].
passing just parseInt as a callback.. how does it know what arguments to take?
This answer on StackOverflow gives the correct reasoning: stackoverflow.com/a/262511/910328