From 307b13584937452f60206a8d03382ebbc658e447 Mon Sep 17 00:00:00 2001 From: Johannes Andersson Date: Sat, 3 Jul 2021 00:26:56 +0200 Subject: [PATCH] Docs typo on dst weirdness (#962) --- docs/zones.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/zones.md b/docs/zones.md index 57305e19a..1c3bf2a0d 100644 --- a/docs/zones.md +++ b/docs/zones.md @@ -228,7 +228,7 @@ Most of the time, DST shifts will happen without you having to do anything about ### Invalid times -Some local times simply don't exist. The Spring Forward DST shift involves shifting the local time forward by (usually) one hour. In my zone, `America/New_York`, on March 12, 2017 the millisecond after 1:59:59.999 is 3:00:00.000. Thus the times between 2:00:00.000 and 2:59:59.000, inclusive, don't exist in that zone. But of course, nothing stops a user from constructing a DateTime out of that local time. +Some local times simply don't exist. The Spring Forward DST shift involves shifting the local time forward by (usually) one hour. In my zone, `America/New_York`, on March 12, 2017 the millisecond after 1:59:59.999 is 3:00:00.000. Thus the times between 2:00:00.000 and 2:59:59.999, inclusive, don't exist in that zone. But of course, nothing stops a user from constructing a DateTime out of that local time. If you create such a DateTime from scratch, the missing time will be advanced by an hour: