Why is using “for…in” with array iteration a bad idea in javascript?

Using for..in loops in JavaScript with array iteration is a bad idea because of the following behavior −

Using normal iteration loops −

Example

let arr = []
arr[4] = 5
for (let i = 0; i < arr.length; i ++) {
   console.log(arr[i])
}

Output

undefined
undefined
undefined
undefined
5

If we had iterated over this array using the for in construct, we'd have gotten −

Example

let arr = []
arr[4] = 5
for (let i in arr) {
   console.log(arr[i])
}

Output

5

Note that the length of the array is 5, but this still iterates over only one value in the array.

This happens because the purpose of the for-in statement is to enumerate over object properties. This statement will go up in the prototype chain, also enumerating over inherited properties, a thing that sometimes is not desired.

Ayush Gupta

Updated on 19-Sep-2019 06:57:52

• Related Questions & Answers
• Why is using “for…in” loop in JavaScript array iteration a bad idea?
• Why is using the JavaScript eval() function a bad idea?
• Why importing star is a bad idea in python
• Why circular reference is bad in javascript?
• Why eating the raw food is bad for health?
• Why do I sweat too much, Is it bad for me?
• Why are "continue" statements bad in JavaScript?
• Why “using namespace std” is considered bad practice in C++
• Why combination of twitter and facebook is bad
• Why do you think privatization of education is bad?
• Why is it bad to watch TV while eating?
• Why are women considered bad drivers?
• Why python for loops don't default to one iteration for single objects?
• Iteration of for loop inside object in JavaScript to fetch records with odd CustomerId?
• What is IDEA in Information Security?