Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115177
MIME-Version: 1.0
References: <CAF+90c-W_g9Mt9yMNzBWfMEmQP287a7A6S75RyZo2fvUO2uGXQ@mail.gmail.com>
 <CAF+90c8eE_J-ntY=E8rtusAzh_6mJUKRmYhtunyAV2dPK7LN5Q@mail.gmail.com>
In-Reply-To: <CAF+90c8eE_J-ntY=E8rtusAzh_6mJUKRmYhtunyAV2dPK7LN5Q@mail.gmail.com>
Date: Mon, 28 Jun 2021 18:17:16 +0200
Message-ID: <CAOWwgpkiMhrQ-zyww8G4aSEcVgKwsr=sagoEZb1r5fszvgOsmA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006096a105c5d5d314"
Subject: Re: [PHP-DEV] Re: [RFC] Readonly properties
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--0000000000006096a105c5d5d314
Content-Type: text/plain; charset="UTF-8"

> > I'd like to open the discussion on readonly properties:
> > https://wiki.php.net/rfc/readonly_properties_v2
> >
> > This proposal is similar to the
> > https://wiki.php.net/rfc/write_once_properties RFC that has been
> declined
> > previously. One significant difference is that the new RFC limits the
> scope
> > of initializing assignments. I think a key mistake of the previous RFC
> was
> > the confusing "write-once" framing, which is both technically correct and
> > quite irrelevant.
> >
> > Please see the rationale section (
> > https://wiki.php.net/rfc/readonly_properties_v2#rationale) for how this
> > proposal relates to other RFCs and alternatives.
> >
>
> I plan to open voting on this RFC soon. I don't think there's anything
> technical left to address here, the discussion mostly comes down to a value
> judgement. I think everyone has made their position regarding that clear...
>

Actually, we talked off the list about a way to possibly make this work
with __clone():

We could allow __clone to have one argument, the object being cloned. And
when the signature declares this argument, then all readonly properties
would be set as uninitialized on $this.

A typical __clone function would look like this with readonly properties:
function __clone(object $original)
{
    $this->readonlyProp = clone $original->readonlyProp;
}

That would turn my vote into a +1 if that could be made to work!

Cheers,
Nicolas

--0000000000006096a105c5d5d314--