Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127831
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_72773951-B30F-41A0-9BD2-D17A967083CB"
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: [PHP-DEV] Pre-RFC: allow #[Override] on properties
Message-ID: <00B391BA-EB1E-4B2B-82D6-4583661603AB@jiripudil.cz>
Date: Wed, 2 Jul 2025 09:50:18 +0200
To: internals@lists.php.net
From: me@jiripudil.cz (=?utf-8?B?SmnFmcOtIFB1ZGls?=)


--Apple-Mail=_72773951-B30F-41A0-9BD2-D17A967083CB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi internals,

I would like to propose extending the target of the #[Override] =
attribute to include properties.

The original RFC explicitly excluded properties [1] for reasons that =
have since then changed drastically: the additions in 8.4 have allowed =
properties to become a more prominent part of the public API of a class =
or an interface. In light of these changes, I believe it might be worth =
revisiting.

The RFC passed almost unanimously, but based on the discussion, I got =
the impression it raised some concerns about its utility. So I wanted to =
reach out and read the room before proceeding with an actual RFC.

Looking forward to your thoughts.

Best regards,

Ji=C5=99=C3=AD Pudil

[1] https://wiki.php.net/rfc/marking_overriden_methods#properties


--Apple-Mail=_72773951-B30F-41A0-9BD2-D17A967083CB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;">Hi =
internals,<br><br>I would like to propose extending the target of the =
#[Override] attribute to include properties.<br><br>The original RFC =
explicitly excluded properties [1] for reasons that have since then =
changed drastically: the additions in 8.4 have allowed properties to =
become a more prominent part of the public API of a class or an =
interface. In light of these changes, I believe it might be worth =
revisiting.<br><br>The RFC passed almost unanimously, but based on the =
discussion, I got the impression it raised some concerns about its =
utility. So I wanted to reach out and read the room before proceeding =
with an actual RFC.<br><br>Looking forward to your thoughts.<br><br>Best =
regards,<br><br>Ji=C5=99=C3=AD Pudil<br><br>[1]&nbsp;<a =
href=3D"https://wiki.php.net/rfc/marking_overriden_methods#properties">htt=
ps://wiki.php.net/rfc/marking_overriden_methods#properties</a><div><br></d=
iv></body></html>=

--Apple-Mail=_72773951-B30F-41A0-9BD2-D17A967083CB--