Skip to content

Changed wrong/confusing prime factors instructions#1468

Closed
ananaft wants to merge 1 commit intoexercism:mainfrom
ananaft:update-prime-factors-instructions
Closed

Changed wrong/confusing prime factors instructions#1468
ananaft wants to merge 1 commit intoexercism:mainfrom
ananaft:update-prime-factors-instructions

Conversation

@ananaft
Copy link

@ananaft ananaft commented Feb 18, 2026

Issue: The current instructions consider 4 a possible prime factor, despite it not being a prime number.

Fix: Remove lines mentioning 4 as a possible factor.

@wolf99
Copy link
Contributor

wolf99 commented Feb 18, 2026

I think perhaps you have misunderstood. This sentence is explaining that 4 is a possible factor of 60 but that it is not a prime number so 4 should be discounted.

@ananaft
Copy link
Author

ananaft commented Feb 19, 2026

The current wording makes it seem like the exclusion criterion for the number 4 is the fact that it does not go cleanly into 5. This at least made me double check the exact definition of prime factors elsewhere before continuing with the exercise.

@ananaft
Copy link
Author

ananaft commented Feb 19, 2026

I now realize that the current wording serves as a good hint on how to possibly design the solution algorithm. Checking whether a possible factor is actually a prime number would be redundant. I sincerely apologize for being nitpicky and possibly bothersome. Thank you for your time, nonetheless!

@ananaft ananaft closed this Feb 19, 2026
@ananaft ananaft deleted the update-prime-factors-instructions branch February 19, 2026 11:11
@siebenschlaefer
Copy link
Contributor

@ananaft No worries.

BTW the description and tests cases of the practice exercises come from the language-agnostic problem-specifications repository.

If you want to report an error or suggest an improvement that is not specific to the C track please post on the forum first before creating an issue or pull request. That's where the maintainers want to keep these discussions.

@ananaft
Copy link
Author

ananaft commented Feb 20, 2026

Thanks for the information!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants