Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120405
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-441-ga3ab13cd6d-fm-20230517.001-ga3ab13cd
Mime-Version: 1.0
Message-ID: <0a54d9a6-98f0-4580-af6a-09435c82bf63@app.fastmail.com>
In-Reply-To: 
 <SYCP282MB0573156E320AECFE12290391BC449@SYCP282MB0573.AUSP282.PROD.OUTLOOK.COM>
References: 
 <SYCP282MB0573156E320AECFE12290391BC449@SYCP282MB0573.AUSP282.PROD.OUTLOOK.COM>
Date: Sat, 27 May 2023 12:24:23 -0500
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] RFC [Concept] - Interface Properties
From: larry@garfieldtech.com ("Larry Garfield")

On Sat, May 27, 2023, at 1:39 AM, Nick Humphries wrote:
> Hello internals,
>
> Based on a few discussions I've had recently, my team and I couldn't 
> think of any reason why we shouldn't have properties on interfaces as 
> it is common for these to be specified in doc blocks currently. 
> Timing-wise, this lines up well with dynamic properties being 
> depreciated. 
>
> I've thrown together a very quick POC, there are many tests and 
> examples of how this could look. 
>
> https://github.com/php/php-src/compare/master...Humni:php-src:feature/rfc-interface-properties
>
> Some of the key architectural decisions:
> - interfaces can implement the same property (exact type match only)
> - interface properties must be public
> - interface properties can't be static
> - interface properties can be readonly
>
> Open to feedback from everyone on this - keen to get the ball rolling 
> quickly on it! 

Interface properties are already included in the Property Hooks RFC, which should be going to a vote soon-ish.  We hope it passes, of course. :-)

https://wiki.php.net/rfc/property-hooks

--Larry Garfield