Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121705
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
In-Reply-To: <A397ECDD-B260-41CF-84C0-6340CB62C561@gmail.com>
Date: Fri, 17 Nov 2023 14:30:42 +0100
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <C01412DB-E7BA-4E89-ADE2-67F753D3B279@gmail.com>
References: <2b4591c1-f999-49b5-8061-67db816aa0da@gmail.com>
 <CAEKnhAE9UifgLQJ4yaxC9OrWt1gQiDVo4crSLAUoDyJ_UQadbQ@mail.gmail.com>
 <A397ECDD-B260-41CF-84C0-6340CB62C561@gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Subject: Re: [PHP-DEV] [RFC][Discussion] Harmonise "untyped" and "typed"
 properties
From: claude.pache@gmail.com (Claude Pache)



> Le 17 nov. 2023 =C3=A0 11:47, Rowan Tommins <rowan.collins@gmail.com> =
a =C3=A9crit :
>=20
> On 16 November 2023 21:38:48 GMT, Jakub Zelenka <bukka@php.net> wrote:
>> This sounds like a huge BC break. Probably bigger and a bit harder to =
fix
>> than disallowing dynamic props.
>=20
> More common, maybe; but trivial to fix: add "=3Dnull" at the end of =
all untyped property declarations that don't already have an =
initializer. It would be trivial to automate with something like Rector.
>=20

The fix is trivial, but the number of files to be touched is huge.

>=20
>> Maybe it would be better to do this as some sort of opt in behaviour
>=20
> We already have the opt-in behaviour: add "mixed" to a property =
declaration, and it no longer gets initialized to null. [...]
>=20

Yes, except that an untyped (respectively `mixed`) property cannot be =
redeclared as `mixed` (resp. untyped) in a subclass. A small step in the =
right direction is to allow that.

=E2=80=94Claude