I forgot to mention that on the flip side, this would allow `public
public(set) readonly` properties to be "overwritten" after __clone touched
them; which is why we chose the more "locked down" version in the first
place. So I want to consider this before just updating the RFC :)
On Fri, May 16, 2025 at 9:41 PM Nicolas Grekas
wrote:
Being able to update a readonly property even if __clone already touched it
> looks critical to me because otherwise, it'd mean that adding a __clone
> method after publishing a first version of some class that has no __clone
> method would be
Hi,
Bukka asked me to create an RFC for a pull request I'm working on, so
I'm requesting a bit of RFC karma.
I would like to add a small helper to PHP to return the number of
available CPU threads: https://github.com/php/php-src/pull/11137.
As I'm new to this, I appreciate any points or tip
On 17 May 2025 19:32:21 BST, Daniel Kesselberg wrote:
>Hi,
>
>Bukka asked me to create an RFC for a pull request I'm working on, so I'm
>requesting a bit of RFC karma.
>
>I would like to add a small helper to PHP to return the number of available
>CPU threads: https://github.com/php/php-src/pull
