Add solution for Challenge 6 by clgp-aint-cool

[clgp-aint-cool]

Challenge 6 Solution

Submitted by: @clgp-aint-cool
Challenge: Challenge 6

Description

This PR contains my solution for Challenge 6.

Changes

• Added solution file to challenge-6/submissions/clgp-aint-cool/solution-template.go

Testing

• Solution passes all test cases
• Code follows Go best practices

Thank you for reviewing my submission! 🚀

[coderabbitai]

Walkthrough

A new Go submission file was added to the challenge-6 directory containing a CountWordFrequency function that normalizes input text by removing apostrophes and converting hyphens to spaces, then counts word frequencies across whitespace-delimited tokens after lowercasing and punctuation trimming.

Changes

Cohort / File(s)	Summary
Word Frequency Counter challenge-6/submissions/clgp-aint-cool/solution-template.go	Added exported function CountWordFrequency(text string) map[string]int that normalizes and counts word frequencies in input text, handling apostrophe removal, hyphen-to-space conversion, and punctuation trimming.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Add solution for Challenge 6 by SleepsOne #1109: Adds the same CountWordFrequency function in package challenge6 with a different implementation in a separate submission file.
• Add solution for Challenge 6 by 0xtrooper #882: Implements the identical CountWordFrequency function in package challenge6 with near-identical preprocessing and word-counting logic.
• Add solution for Challenge 6 by ansmonjol #757: Adds the same CountWordFrequency function in package challenge6 with similar word-frequency logic and differing token-cleaning details.

Poem

🐰 A function hops in, counting words with care,
Apostrophes stripped, hyphens split with flair,
Letters tumble down to lowercase rest,
Frequency maps emerge, each word assessed! 📊

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a solution submission for Challenge 6 by the specified user.
Description check	✅ Passed	The description is directly related to the changeset, providing context about the Challenge 6 submission and the file being added.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 69fc28ed-6374-40fa-a672-da70b9811ef4

📥 Commits

Reviewing files that changed from the base of the PR and between 6a002af and 117a34e.

📒 Files selected for processing (1)

• challenge-6/submissions/clgp-aint-cool/solution-template.go

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

In Go's standard library, does strings.Trim remove cutset characters only from the beginning and end of a string (and not from the middle)?

💡 Result:

Yes. In Go’s standard library, strings.Trim(s, cutset) only removes characters in cutset from the start and end of s (“all leading and trailing Unicode code points contained in cutset removed”)—it does not remove matching characters from the middle of the string. [1]

Source: [1]

---

🏁 Script executed:

cat -n challenge-6/submissions/clgp-aint-cool/solution-template.go | head -35

Repository: RezaSi/go-interview-practice

Length of output: 1391

---

Normalization misses non-trimmed characters and can count empty keys.

The function contract (lines 14–17) requires that "all punctuation, spaces, and other non-alphanumeric characters are ignored." However, line 28's strings.Trim() only removes the specified punctuation from token boundaries, leaving internal non-alphanumeric characters untouched. For example, characters like / in "go/go" remain inside the token, violating the contract. Additionally, line 29 can increment wordFreq[""] when a token consists entirely of characters in the trim set.

Use strings.Map() with unicode.IsLetter() and unicode.IsDigit() to treat all non-alphanumeric characters as separators, ensuring proper normalization.

[github-actions]

🎉 Auto-merged!

This PR was automatically merged after 2 days with all checks passing.

Thank you for your contribution, @clgp-aint-cool!