TryBugHunt
goNull / UndefinedEasy

Word counter crashes on the first word

BugFind the bug and fix the code

What it should do

wordFrequency(text) counts how often each word appears, ignoring case. wordFrequency("the cat the dog") returns {"the": 2, "cat": 1, "dog": 1}.

What happens instead

wordFrequency("the cat the dog") crashes with panic: assignment to entry in nil map.

package main

import "strings"

func wordFrequency(text string) map[string]int {
    var counts map[string]int
    for _, w := range strings.Fields(strings.ToLower(text)) {
        counts[w]++
    }
    return counts
}

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 null and undefined errors pattern

A nil pointer or nil map that the code uses as if it held a value.

What you'll practise

An easy Go debugging exercise about null and undefined errors: a nil pointer or nil map that the code uses as if it held a value.

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)

var counts map[string]int declares a map but does not create one: its value is nil. Reading a nil map is allowed and returns zero values, but writing to it panics, so the first counts[w]++ crashes. For empty text nothing is written, and the function returns nil, which is JSON null rather than {}. Create maps with map[string]int{} or make(map[string]int) before writing. Slices are different: append works on a nil slice, which is why this catches people who learned slices first.

The pattern behind it: null and undefined errors.

More null and undefined errors to practise

Seen this error in your own code?

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/4ee97bc1-f4d1-4652-bbf4-d1c0977de7f2" title="Debugging challenge: Word counter crashes on the first word" 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/4ee97bc1-f4d1-4652-bbf4-d1c0977de7f2">TryBugHunt</a></p>