Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109102
MIME-Version: 1.0
References: <CAH5C8xVY5SFLBt2jZ9dx93rQC_Xjp4pKZJ+MP=K1TbjyDi9CDA@mail.gmail.com>
In-Reply-To: <CAH5C8xVY5SFLBt2jZ9dx93rQC_Xjp4pKZJ+MP=K1TbjyDi9CDA@mail.gmail.com>
Date: Tue, 17 Mar 2020 14:03:37 +0100
Message-ID: <CAOWwgpmBMB3iPyg+GoL=39u68yUX1ERCs2-csENTJ04PmS4xMA@mail.gmail.com>
To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000023c90805a10c91bd"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Immutable/final/readonly properties
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--00000000000023c90805a10c91bd
Content-Type: text/plain; charset="UTF-8"

> I believe we had a long enough and fruitful discussion period,
> so I have just opened the vote at
> https://wiki.php.net/rfc/write_once_properties
> since I didn't want to add any significant change to the proposal
> any more.
>
> The vote will run for 2 weeks and it will be closed on 2020-03-31.
>

Hi everyone,

I voted against the RFC because it has too many rough edges to me.
eg cloning doesn't work, the initialization needs special rules, etc.

I don't think these issues can nor should be figured out later on: they are
low-level conceptual issues IMHO.
We should not build on them before they're resolved (a land field of
special cases look like a big code smell to me).

I proposed an alternative behavior that removes all the issues.
I think it needs to be discussed more in-depth:
https://externals.io/message/108675#108753

Regards,
Nicolas

--00000000000023c90805a10c91bd--