Hi everyone,
I am posting this as an “intent to vote” email to announce that
the voting process of this RFC will be opened at 15 Sept if no
further opinions/objections emerge.
RFC: https://wiki.php.net/rfc/reldateformatter
I hope you love this RFC 
Cheers,
Weilin Du
Hi
On 2026-09-07 19:19, Weilin Du wrote:
I am posting this as an "intent to vote" email to announce that
the voting process of this RFC will be opened at 15 Sept if no
further opinions/objections emerge.
Similarly to the PREG_THROW_ON_ERROR one, I didn't yet get around to this one after my vacation. I've given it a very quick read, but not much thought. One point for now:
The RFC specifies that the given ICU UNumberFormat is cloned internally. Does that mean if I pass in a NumberFormatter instance and later reconfigure using `->setAttribute()`, the changes will not be applied to IntlRelativeDateTimeFormatter? I believe this would be very unexpected behavior.
Best regards
Tim Düsterhus
Hi Tim,
Yes. The clone was necessary because ICU takes ownership
of the UNumberFormat passed to it.
And yes, this would be unexpected. Technically it is possible
for us to fix this in the php side. My idea is to make the internal
ICU formatter refreshed lazily before the next format() or
formatnumeric() call, and by refreshing we observe if there is
updates to the internal retained numberformatter.
I think this is a good catch user-side. Will add this in the RFC
and implementation. Thanks!
Weilin