Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110784
MIME-Version: 1.0
References: <CAHRtwKbbsoh4kT5++43yJg9RH+aNnRCAiE+yLOO7tOfMjcjBGg@mail.gmail.com>
 <CADyq6sKXtrc4tb5ukBtxmNb9PqpRFP2R9MvGRfdwpuGGv-YJnQ@mail.gmail.com> <CALKiJKooXcJuOX1MoF4aHHWsG+b0m6+_hBkLDqi25Xt7K0SqYg@mail.gmail.com>
In-Reply-To: <CALKiJKooXcJuOX1MoF4aHHWsG+b0m6+_hBkLDqi25Xt7K0SqYg@mail.gmail.com>
Date: Mon, 29 Jun 2020 18:21:42 +0200
Message-ID: <CADyq6sJzMRyQgWRAc_LUyC7pn+4CpOgvuw=ZejtAFOjzUFpTFQ@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000000e6fb05a93b757c"
Subject: Re: [PHP-DEV] [RFC] Property write visibility
From: ocramius@gmail.com (Marco Pivetta)

--00000000000000e6fb05a93b757c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey Rowan,

On Mon, Jun 29, 2020, 18:19 Rowan Tommins <rowan.collins@gmail.com> wrote:

> On Mon, 29 Jun 2020 at 16:44, Marco Pivetta <ocramius@gmail.com> wrote:
>
> > property accessors seem to perpetuate the bad practice
> > of getters and setters
> >
>
>
> Outside of access restrictions, a common use case I've seen for property
> accessors is lazy-loading, which I know is something you use in other
> forms.
>

I had already tested the write-once properties RFC with lazy-loading: works
just fine =F0=9F=91=8D

>

--00000000000000e6fb05a93b757c--