Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync leap with problem-specifications #1853

Merged
merged 1 commit into from
Jan 15, 2024
Merged

Sync leap with problem-specifications #1853

merged 1 commit into from
Jan 15, 2024

Conversation

senekor
Copy link
Contributor

@senekor senekor commented Jan 14, 2024

A bunch of test cases not part of problem-specifications were deleted. Looking through the git history, it seems the manual cases were added first and the ones from problem-specfications later. Some cases are even duplicated because of this. I checked if there are some interesting edge cases worth upstreaming. The most likely ones would be:

process_leapyear_case(1, false);
process_leapyear_case(4, true);

problem-specifications doesn't yet have any test cases close to the year zero. That being said, I can't think of a concrete solution that would fail these test cases. So it might not be worth upstreaming after all.

@senekor senekor merged commit 636c2e7 into main Jan 15, 2024
11 checks passed
@senekor senekor deleted the leap-sync branch January 15, 2024 08:39
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.

2 participants