The tests in clock do not test whether integer overflows are handles correctly. If these test are welcome, I’d be happy to implement them.
Cheers
When you say overflow, do you mean the number is bigger than 32/64 bits or that it wraps around past 60 and 24?
This problem likely comes from the problem spec which doesn’t contain language specific edge cases. Many tracks stick to what is in the problem specs.
Hi,
yes, I was referring to integer overflows. I get your point about the language specifics and not trying to make production-grade software in the docs. Fair enough :). Was just an idea…
Yup. Thank you for sharing the idea!
That linked doc also comments on what sort of things make sense to extend the tests with. Adding every possible “production level checks” to exercises distracts from the actual focus of the specific exercises and turns them all into more generic “how much input validation is possible” exercises, which isn’t helpful in the broader view.