Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108692
MIME-Version: 1.0
References: <CAH5C8xVYFkgyW88332ei8coMOijuynHXg3A2dL50XU4HP5Vpyw@mail.gmail.com>
In-Reply-To: <CAH5C8xVYFkgyW88332ei8coMOijuynHXg3A2dL50XU4HP5Vpyw@mail.gmail.com>
Date: Wed, 19 Feb 2020 19:26:25 -0500
Message-ID: <CAKuGYLTsK2h_Yeo1vMju867hhmzyHt+GwoGStcQtiYMi2VB1tg@mail.gmail.com>
To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003a6ec8059ef6f571"
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Immutable/final/readonly properties
From: matthewmatthew@gmail.com (Matthew Brown)

--0000000000003a6ec8059ef6f571
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Someone recently requested something similar for a PHP static analysis tool
I wrote (https://psalm.dev/r/f75997a263), though that version only allows
lazy initialisation inside the class in which a given property is declared.

Personally I don't like either approach =E2=80=93 I think per-property gett=
ers and
setters would be a more appropriate venue for this functionality, something
like:

property int $s {
    public get;
    private set;
}

This pattern could also be extended to support per-property getter and
setter methods.

On Wed, 19 Feb 2020 at 12:06, M=C3=A1t=C3=A9 Kocsis <kocsismate90@gmail.com=
> wrote:

> Hi Internals,
>
> I'd like to move my RFC forward to the discussion phase:
> https://wiki.php.net/rfc/write_once_properties
>
> In short, I propose to add support for a new property modifier that would
> allow properties to be initialized, but not modified afterwards.
>
> Cheers,
> M=C3=A1t=C3=A9 Kocsis
>

--0000000000003a6ec8059ef6f571--