TryBugHunt
goOff-by-oneHard

Text wrapping breaks lines that would fit exactly

BugFind the bug and fix the code

What it should do

wrapWords(text, width) splits text into lines of at most width characters without breaking words. wrapWords("the cat sat on the mat", 7) returns ["the cat", "sat on", "the mat"].

What happens instead

wrapWords("hello world", 11) returns ["hello", "world"] even though "hello world" is exactly 11 characters.

package main

import "strings"

func wrapWords(text string, width int) []string {
    lines := []string{}
    line := ""
    for _, w := range strings.Fields(text) {
        if line == "" {
            line = w
        } else if len(line)+1+len(w) < width {
            line += " " + w
        } else {
            lines = append(lines, line)
            line = w
        }
    }
    if line != "" {
        lines = append(lines, line)
    }
    return lines
}

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 off-by-one errors pattern

The loop that runs one time too many, the slice that drops the last item, the index that starts in the wrong place.

What you'll practise

A hard Go debugging exercise about off-by-one errors: the loop that runs one time too many, the slice that drops the last item, the index that starts in the wrong place.

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)

A word fits on the current line if the line, one space and the word together are no longer than width. "At most width" means <=, but the code uses <, so a line that would be exactly width characters long is treated as too long and wrapped early. Most real text rarely lands on the exact limit, so the bug looks like occasional odd wrapping. When a rule says "at most" or "up to", write <=; when it says "less than", write <. Always test the boundary value itself.

The pattern behind it: off-by-one errors.

More off-by-one errors to practise

Related errors

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/fb8a34ee-6ed4-49fe-9af8-1fd466da6c32" title="Debugging challenge: Text wrapping breaks lines that would fit exactly" 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/fb8a34ee-6ed4-49fe-9af8-1fd466da6c32">TryBugHunt</a></p>