> Hi > Thank you. I've had a look at the changes you made and I'm noticing that > you added a second voting widget by accident. Can you double-check the > diff and revert the accidental changes?
> https://wiki.php.net/rfc/const_object_property_write?do=diff&rev2%5B0%5D=1775894869&rev2%5B1%5D=1782632547&difftype=sidebyside > I'm also noticing just now that the RFC is not listed in the RFC > overview at https://wiki.php.net/rfc (and itself has the status > “Draft”). Can you make sure to list the RFC in “Under Discussion”? It > could technically be argued that the discussion didn't properly happen, > but as you made a recent change that resets the cooldown anyway and > there's still a bit of time until feature freeze that shouldn't be an > issue. Hi Tim, Thanks for catching these. I removed the accidental duplicate voting content and added the RFC to the “Under Discussion” section of the RFC overview page. Best regards, __ *Khaled Alam* On Mon, Jun 29, 2026 at 11:55 PM Tim Düsterhus <[email protected]> wrote: > Hi > > Am 2026-06-28 09:50, schrieb Khaled Alam: > > I've updated the PR (#20903) and bumped the RFC > > <https://wiki.php.net/rfc/const_object_property_write> to v0.3 to cover > > this. Since it widens the scope, > > I'll restart the discussion cooldown and push the vote date back > > accordingly. > > Thank you. I've had a look at the changes you made and I'm noticing that > you added a second voting widget by accident. Can you double-check the > diff and revert the accidental changes? > > > https://wiki.php.net/rfc/const_object_property_write?do=diff&rev2%5B0%5D=1775894869&rev2%5B1%5D=1782632547&difftype=sidebyside > > I'm also noticing just now that the RFC is not listed in the RFC > overview at https://wiki.php.net/rfc (and itself has the status > “Draft”). Can you make sure to list the RFC in “Under Discussion”? It > could technically be argued that the discussion didn't properly happen, > but as you made a recent change that resets the cooldown anyway and > there's still a bit of time until feature freeze that shouldn't be an > issue. > > Best regards > Tim Düsterhus >
