Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122793
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-333-gbfea15422e-fm-20240327.001-gbfea1542
Precedence: bulk
MIME-Version: 1.0
Message-ID: <39d48e89-62d8-4fc1-b8b7-59cc25e106c2@app.fastmail.com>
In-Reply-To: <E750EF7A-39B2-44BA-8888-9A4D31591338@sakiot.com>
References: <E750EF7A-39B2-44BA-8888-9A4D31591338@sakiot.com>
Date: Thu, 28 Mar 2024 15:15:59 +0000
To: "php internals" <internals@lists.php.net>
Subject: Re: [PHP-DEV] Allow properties to be defined on interface
Content-Type: text/plain
From: larry@garfieldtech.com ("Larry Garfield")

On Thu, Mar 28, 2024, at 3:03 PM, Saki Takamachi wrote:
> Hi internals,
>
> With read-only properties, we no longer need to define getter methods 
> when we can take advantage of them.
>
> However, there is still one problem here from a convenience standpoint. 
> That is if we use an interface, we still need to define a getter method.
>
> This was mentioned by @sakurairo in X
>
>
> Therefore, I propose to allow public properties to be defined on the 
> interface (It does not matter whether it is read-only or not).
>
> I would like to hear your feedback.
> Also, if a similar discussion has taken place before, I would 
> appreciate it if you could let me know.
>
> Regards.
>
> Saki

This functionality is included in the Property Hooks RFC, which will be going to a vote just as soon as Ilija finishes polishing up the test suite for it.  (I think he wants to get it into a "commit as soon as the vote passes" state before we call the vote, even though that's not process-required.)

https://wiki.php.net/rfc/property-hooks#interfaces

--Larry Garfield