3 ms·
> When I read the initial %G post - I couldn't see how you could/would even test for it - unless you'd heard about such a scenario previously. Interestingly, b
by masklinn 9y ago
> When I read the initial %G post - I couldn't see how you could/would even test for it - unless you'd heard about such a scenario previously.
Interestingly, because IIRC the Gregorian calendar has a 400 years "full" cycle (hence the "Doomsday Rule") depending on the "expense" of your processes you could just use exhaustive testing: there are less than 150k days in 400 gregorian years. Considering exhaustive testing is feasible across 32b ranges (https://randomascii.wordpress.com/2014/01/27/theres-only-four-billion-floatsso-test-them-all/ https://randomascii.wordpress.com/2014/01/27/theres-only-fou...), ~17 bits isn't much of an issue.
You would still need to define properties which hold across the board, but then you could just check literally every date of the cycle.
This get significantly less feasible if you need to check full calendaring (datetime x timezones).