Add solution for Challenge 1 by cckwes

[cckwes]

Challenge 1 Solution

Submitted by: @cckwes
Challenge: Challenge 1

Description

This PR contains my solution for Challenge 1.

Changes

• Added solution file to challenge-1/submissions/cckwes/solution-template.go

Testing

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

Thank you for reviewing my submission! 🚀

[coderabbitai]

Walkthrough

Adds a new Go submission file that defines an exported Sum(a int, b int) int and a main that reads two comma-separated integers from stdin using "%d, %d", handles read errors, computes their sum via Sum, and prints the result.

Changes

Cohort / File(s)	Summary
Challenge 1 submission challenge-1/submissions/cckwes/solution-template.go	New file adding Sum(a int, b int) int and a main entrypoint. main parses two ints from stdin with fmt.Scanf("%d, %d", &a, &b), exits on parse error, calls Sum(a,b), and prints the result.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Check Sum correctness (straight addition)
• Verify fmt.Scanf format, error handling, and output formatting
• Consider integer overflow/edge-case inputs if applicable

Possibly related PRs

• Add solution for Challenge 1 by greenfivebird #817 — Adds an identical exported Sum(a int, b int) int and a main that reads "%d, %d" and prints Sum in a Challenge 1 submission.
• Add solution for Challenge 1 by elecycele #795 — Adds a Go solution-template.go with the same Sum signature and main I/O behavior for Challenge 1.
• Add solution for Challenge 1 by rizkyfauziilmi #725 — Introduces the same exported Sum(a int, b int) int and similar main parsing/printing logic in a parallel submission.

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a solution for Challenge 1 by the contributor cckwes, which directly matches the changeset content.
Description check	✅ Passed	The description is clearly related to the changeset, explaining the Challenge 1 solution submission with details about the file location, testing, and coding standards.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1043be5 and 45c985a.

📒 Files selected for processing (1)

• challenge-1/submissions/cckwes/solution-template.go (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• challenge-1/submissions/cckwes/solution-template.go

---

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: 2

🧹 Nitpick comments (2)

challenge-1/submissions/cckwes/solution-template.go (2)

12-13: Consider using a non-zero exit code on error.

Returning from main exits with status 0 even when an error occurs. For better error signaling, consider os.Exit(1) after printing the error message. This is a minor improvement for observability.

---

22-23: Integer overflow is theoretically possible but acceptable for this challenge.

Go's int type can overflow silently (e.g., math.MaxInt + 1 wraps to math.MinInt). For a coding challenge focused on basic addition, this edge case is likely out of scope, but worth noting for production code.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7b8b26a and 1043be5.

📒 Files selected for processing (1)

• challenge-1/submissions/cckwes/solution-template.go (1 hunks)

🔇 Additional comments (1)

challenge-1/submissions/cckwes/solution-template.go (1)

1-5: LGTM!

Package declaration and imports are correct and follow Go conventions.