Add solution for Challenge 1 by yz4230

[yz4230]

Challenge 1 Solution

Submitted by: @yz4230
Challenge: Challenge 1

Description

This PR contains my solution for Challenge 1.

Changes

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

Testing

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

Thank you for reviewing my submission! 🚀

[coderabbitai]

Warning

Rate limit exceeded

@yz4230 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 23 minutes and 4 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 800774e and 9e803c6.

📒 Files selected for processing (1)

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

Walkthrough

A new Go program solution-template.go is added to the Challenge 1 submission directory. It reads two comma-separated integers from standard input, computes their sum using a newly added Sum function, and outputs the result.

Changes

Cohort / File(s)	Summary
New Challenge 1 Solution challenge-1/submissions/yz4230/solution-template.go	Introduces Sum(a int, b int) int function and a main CLI that parses two integers via fmt.Scanf, calls Sum, and prints the result.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file with simple, straightforward logic: basic input parsing, a trivial arithmetic operation, and output
• No complex control flow or edge cases to evaluate

Possibly related PRs

• Add solution for Challenge 1 by eksly #621: Adds identical Challenge 1 solution with the same Sum(a int, b int) int function and nearly identical main scaffolding using fmt.Scanf("%d, %d").
• Add solution for Challenge 1 by rizkyfauziilmi #725: Introduces the same exported Sum(a int, b int) int with equivalent main wiring to read and sum two integers.
• Add solution for Challenge 1 by Dhar01 #737: Adds the same Sum(a int, b int) int function and main CLI that reads two ints and prints their sum, differing only in internal validation logic.

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies that this PR adds a solution for Challenge 1 by the user yz4230, which matches the changeset content.
Description check	✅ Passed	The description is directly related to the changeset, explaining that it contains a solution for Challenge 1 and specifying the file location.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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

🧹 Nitpick comments (2)

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

11-14: Consider writing error messages to stderr.

Error messages should typically be written to stderr (os.Stderr) rather than stdout to keep the output stream clean for the actual result. This follows Go best practices and makes it easier to separate errors from valid output in scripts or pipelines.

Apply this diff to send errors to stderr:

+import (
+	"fmt"
+	"os"
+)
+
 func main() {
 	var a, b int
 	// Read two integers from standard input
 	_, err := fmt.Scanf("%d, %d", &a, &b)
 	if err != nil {
-		fmt.Println("Error reading input:", err)
+		fmt.Fprintln(os.Stderr, "Error reading input:", err)
+		os.Exit(1)
-		return
 	}

---

22-22: Consider using idiomatic Go parameter style.

When multiple parameters share the same type, Go style typically groups them: Sum(a, b int) instead of Sum(a int, b int).

Apply this diff for more idiomatic Go:

-func Sum(a int, b int) int {
+func Sum(a, b int) int {

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9b711a4 and 800774e.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

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

16-18: LGTM!

The Sum function call and output logic are correct and straightforward.