Re: [RFC] Allow Reassignment of Promoted Readonly Properties in Constructor
| From: | Nicolas Grekas | Date: | Mon, 02 Feb 2026 21:14:03 +0000 |
| Subject: | Re: [RFC] Allow Reassignment of Promoted Readonly Properties in Constructor | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-129982@lists.php.net to get a copy of this message | ||
Hi Marco,
Le lun. 2 févr. 2026 à 11:54, Marco Pivetta <ocramius@gmail.com> a écrit :
> Hey Nicolas,
>
>
> On Thu, 22 Jan 2026 at 16:34, Nicolas Grekas <nicolas.grekas+php@gmail.com>
> wrote:
>
>> Dear all,
>>
>> Here is a new RFC for you to consider:
>>
>> https://wiki.php.net/rfc/promoted_readonly_constructor_reassign
>>
>
>
> What happens if one calls
$obj->__construct(1, 2, 3) (on an
> already
> instantiated $obj) in the context of this patch?
>
Thanks for asking, I didn't think about this. This made me also think about
ReflectionClass::newInstanceWithoutConstructor().
I clarified this in the RFC, see "Direct __construct() Calls Cannot Bypass
Readonly" and "Reflection: Objects Created Without Constructor".
Patch and PR updated also if anyone wants to run some code where this RFC
can be played with.
Cheers,
Nicolas