Re: [RFC] Time\Instant and Time\Clock
| From: | Tim Düsterhus | Date: | Fri, 25 Sep 2026 08:03:28 +0000 |
| Subject: | Re: [RFC] Time\Instant and Time\Clock | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-132631@lists.php.net to get a copy of this message | ||
Hi
On 2026-09-23 22:15, Larry Garfield wrote:
Instant+Timezone would be the same information that DateTimeImmutable holds, yes. What would likely be another future scope after that is the “calendar-based math” (i.e. the replacement for what's currently DateInterval andFor custom formats, in particular formats with an implied timezone, you’ll need to wait for the future scope “Instant + Timezone” class.I am indeed waiting with baited breath. (That will be the DateTimeImmutable replacement, essentially, yes?)
setDate() and similar) since that's an entire rabbit hole of its own :-)
There is nowhere right now that someone can go to canonically see "oh, they are planning to add a new timezone object and a new DateTimeImmutable replacement later, too. Good to know."Well, it's listed in the Future Scope of this one. And me pointing towards java.time and JavaScript’s Temporal was a sincere answer: The extent of the planning is that it will look somewhat like that and each step is slicing off a small standalone part along the way. Best regards Tim Düsterhus