Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115363
To: internals@lists.php.net
References: <E7988419-8D1A-479B-B81C-07E0C109B686@stitcher.io>
 <0a035a3f-60ef-4001-8c55-f26ab518c3d5@www.fastmail.com>
Message-ID: <5e3ad1ee-1770-ab10-cf27-5f6b870dd13e@processus.org>
Date: Thu, 8 Jul 2021 10:01:48 +0200
MIME-Version: 1.0
In-Reply-To: <0a035a3f-60ef-4001-8c55-f26ab518c3d5@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Subject: Re: [PHP-DEV] Readonly properties and interfaces
From: pierre-php@processus.org (Pierre)

Le 07/07/2021 à 23:16, Larry Garfield a écrit :
> The property accessor RFC (which didn't get to a vote) discussed this, and specifically proposed making properties part of the interface for... basically all the reasons given here.
>
> My preference would be to add property accessors in 8.2 (at least the asymmetric visibility part), and then redefine `readonly` properties as a shorthand for a "get only" implicit accessor property; which, if I recall correctly, is essentially the same semantics as `readonly`.  (I didn't check the RFC; I'm going by memory here.)  That would include interface properties by nature.
>
> --Larry Garfield

Using property accessors on interfaces is fine too, but the one thing 
that properties directly being defined on interfaces do bring is that 
you don't have to repeat implementation of those in your 
implementations. That's a detail, but a practical one.

Regards,

--

Pierre