A loop invariant is a statement that is true before and after each loop iteration. It helps you prove correctness: if it holds initially, stays true each step, and implies the goal at the end, the algorithm is correct.
Advanced answer
Deep dive
Expanding on the short answer — what usually matters in practice:
Context (tags): correctness, invariant, loops
Complexity: compare typical operations (average vs worst-case).
Invariants: what must always hold for correctness.
When the choice is wrong: production symptoms (latency, GC, cache misses).
Explain the "why", not just the "what" (intuition + consequences).
Trade-offs: what you gain/lose (time, memory, complexity, risk).
Edge cases: empty inputs, large inputs, invalid inputs, concurrency.
Examples
A tiny example (an explanation template):
// Example: discuss trade-offs for "what-is-a-loop-invariant-and-why-is-it-useful?"
function explain() {
// Start from the core idea:
// A loop invariant is a statement that is true before and after each loop iteration. It help
}
Common pitfalls
Too generic: no concrete trade-offs or examples.
Mixing average-case and worst-case (e.g., complexity).