TryBugHunt
rustLogic errorEasy

Vector capacity pre-allocation vs length indexing

BugFind the bug and fix the code

What it should do

Allocate vector with capacity n and push items. Example: populate_with_capacity(3) -> [0, 1, 2]

What happens instead

panicked at 'index out of bounds: the len is 0 but the index is 0'

fn populate_with_capacity(n: usize) -> Vec<usize> {
    // Vec::with_capacity allocates memory but sets len to 0; indexing [i] panics
    let mut vec = Vec::with_capacity(n);
    for i in 0..n {
        vec[i] = i;
    }
    vec
}

fn main() {
    println!("{:?}", populate_with_capacity(3));
}

Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).

⏱️0:00
Hints
🏆 0 hints = Flawless Solve
Think & Test Cooldown
2:00 remaining

Take a moment to read the bug symptom and trace the code with Run & Check before unlocking Hint 1.

Hint 2
Unlocks after Hint 1
Hint 3
Unlocks after Hint 2

This bug belongs to the logic errors pattern

The wrong operator, an inverted condition, a formula the right way round but backwards.

What you'll practise

An easy Rust debugging exercise about logic errors: the wrong operator, an inverted condition, a formula the right way round but backwards.

The checks your fix must pass

Signs of this kind of bug

Spoiler: why this bug happens(try it first; the hints get warmer one at a time)

What went wrong: Vec::with_capacity(n) allocates backing memory for n elements, but the vector length is initially 0. Indexing vec[i] checks against len, which is 0, causing an index out of bounds panic.

The fix: Use vec.push(i) to insert elements and increment the length, or initialize with vec![0; n].

Remember: Capacity is not length. You cannot index into uninitialized capacity slots; use push() or initialize elements with a macro.

The pattern behind it: logic errors.

More logic errors to practise

Embed this challenge on your site

Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.

<iframe src="https://trybughunt.com/embed/c49d9f4a-3cf2-4555-ba7e-3bb329126b4d" title="Debugging challenge: Vector capacity pre-allocation vs length indexing" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/c49d9f4a-3cf2-4555-ba7e-3bb329126b4d">TryBugHunt</a></p>