3 ms·
There's nothing broken about parseInt. The problem is, it can take a second argument(radix), and .map will feed it current item's index as the second argument(a
by Fatalist_ma 5y ago
There's nothing broken about parseInt. The problem is, it can take a second argument(radix), and .map will feed it current item's index as the second argument(and the whole array as the third, but that one will get ignored).
const arr = ['1','2','3'];
arr.map(parseInt) is equivalent to: [
parseInt('1', 0, arr),
parseInt('2', 1, arr),
parseInt('3', 2, arr)
];
- antris 5y agoI know why it works this way. I'm not claiming it has a bugged implementation, I'm saying it's broken by design.