Why Modern Languages Are Dropping the C‑Style for Loop

That Infamous Classic Pattern

In C, a for loop packs initialization, condition, and increment on a single line, e.g.:

for (int i = 0; i < 10; i++) {
    printf("%d
", arr[i]);
}

Because all three parts share the same line, it’s easy to forget whether the condition uses < or <=, or whether the step is i++ or i+=2. A tiny slip—writing i<=10 instead of i<10 —can cause an out‑of‑bounds access. The author cites a real embedded‑system bug where an incorrect boundary caused a watchdog reset.

Even worse, the three components can be omitted entirely, yielding for(;;) for an infinite loop, which confuses newcomers.

Modern Languages’ Answer

Language designers observed that 99 % of for‑loop usage is simply iterating over a collection. They therefore removed the need to manage indices, boundaries, and steps manually.

Python introduced a clear, intent‑driven form:

for item in items:
    print(item)

Rust follows a similar idea but with a range syntax:

for i in 0..10 {
    println!("{}", arr[i]);
}

Swift also uses a collection‑oriented loop:

for item in items {
    print(item)
}

Go keeps a C‑style flavor but adds the range keyword to hide index handling:

for i, v := range arr {
    fmt.Println(i, v)
}

All these forms let the programmer say “traverse this collection” without thinking about the underlying mechanics, improving safety and readability.

Deeper Reasons

Safety: The freedom of C’s for loop leads to off‑by‑one errors, infinite loops, and other bugs. By abstracting the iteration, modern loops reduce such mistakes.

Readability: Code is read more often than written. for(int i=0; i<n; i++) forces the reader to translate it mentally into “iterate over an array,” whereas for item in items is self‑explanatory.

Abstraction level: C’s loop is procedural—telling the machine *how* to iterate. Newer loops are declarative—telling the machine *what* to do. This shift reflects a broader evolution toward higher‑level programming paradigms.

Is the C‑Style for Loop Useless?

Not at all. In low‑level or performance‑critical scenarios—such as embedded development, driver code, or when iterating multiple arrays in lockstep—the explicit control of a C‑style loop is valuable. Compilers can also optimise the predictable pattern more aggressively.

How Should Programmers Choose?

If you are writing application‑level code in a modern language, prefer the newer loop constructs for their safety, readability, and lower error surface.

If you are doing systems, embedded, or performance‑sensitive work, the classic C for loop remains a powerful tool because it gives precise control over each iteration.

Regardless of the choice, remember that code is primarily for humans: avoid obscure tricks and keep loops easy to understand.