Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114733
MIME-Version: 1.0
References: <CAF+90c-W_g9Mt9yMNzBWfMEmQP287a7A6S75RyZo2fvUO2uGXQ@mail.gmail.com>
In-Reply-To: <CAF+90c-W_g9Mt9yMNzBWfMEmQP287a7A6S75RyZo2fvUO2uGXQ@mail.gmail.com>
Date: Sat, 5 Jun 2021 10:39:37 +0200
Message-ID: <CAOWwgpnKmB79QSnDjWUwbE9u0m7ZeOVR_6P=fiF6afQcB+r7qQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005e0d0105c400c030"
Subject: Re: [PHP-DEV] [RFC] Readonly properties
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--0000000000005e0d0105c400c030
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Nikita,

Le ven. 4 juin 2021 =C3=A0 17:19, Nikita Popov <nikita.ppv@gmail.com> a =C3=
=A9crit :

> Hi internals,
>
> I'd like to open the discussion on readonly properties:
> https://wiki.php.net/rfc/readonly_properties_v2
>

Thanks for the proposal, that's quite appealing!

I voted "no" on the previous proposal because it didn't play well with
cloning. That's why I favoured asymmetric visibility.
I see that this new iteration has the same issue, so I'd like to know:

What about putting readonly properties in the uninitialized state when
cloning objects?

Cheers,
Nicolas

--0000000000005e0d0105c400c030--