Why JavaScript forEach Cannot Be Interrupted

"This behavior is not a bug or a missing feature. Instead, it reflects the functional nature of the method and the way JavaScript handles callbacks and lexical scopes. Understanding why this happens provides valuable insight into both the design of forEach and the philosophy behind functional programming in JavaScript. The forEach method cannot be interrupted because of its design philosophy. It is a higher-order function, meaning it accepts another function (a callback) as an argument and executes it for each element in the array."

"Control statements such as break and continue are loop-level constructs, valid only inside traditional loops like for, while, or do...while. Since forEach relies on a callback function, not a control flow loop, these statements have no syntactic effect within it. The following simplified implementation illustrates how forEach behaves: Array.prototype.forEach = function (fn, context) { for (let index = 0; index < this.length; index++) { if (index in this) { fn.call(context, this[index], index, this); } } };"

forEach cannot be interrupted by break, continue, or early return because callbacks execute in their own function scope separate from loop-level control. The method is a higher-order function that accepts a callback and invokes it for each array element. Break and continue are valid only inside traditional loop constructs like for, while, or do...while. Because forEach relies on a callback rather than exposed loop syntax, those control statements have no syntactic effect inside the callback. A simplified implementation shows forEach calling fn.call(context, this[index], index, this) inside an internal loop. This design reflects functional programming philosophy and deliberate language scoping behavior.

Read at Substack