Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109118
MIME-Version: 1.0
References: <CAJmjfvW8b=jYTjLfW9N9FT_eQVS7RBe768NZXv-g4V2RM3OgtA@mail.gmail.com>
 <CAJmjfvVekTvzB7FKADyt1dTygORZNK6Hrfh=bWf-PA73HsLQyw@mail.gmail.com> <CABdc3Wpb20HztnkS3T8-ec=FA1K=p_WE7sQs1v6ei6CJDHByZg@mail.gmail.com>
In-Reply-To: <CABdc3Wpb20HztnkS3T8-ec=FA1K=p_WE7sQs1v6ei6CJDHByZg@mail.gmail.com>
Date: Tue, 17 Mar 2020 21:36:21 -0500
Message-ID: <CAJmjfvVL1Kr6F+bM=d-afQHVS=N38-epaioJmr-NBEQweqHBsg@mail.gmail.com>
To: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= <michal.brzuchalski@gmail.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Compact Object Property Assignment
From: jakob@givoni.dk (Jakob Givoni)

Thank you, Micha=C5=82, for chiming in :-)

On Tue, Mar 17, 2020 at 10:52 AM Micha=C5=82 Brzuchalski
<michal.brzuchalski@gmail.com> wrote:
> For object initializer, I was hoping to introduce a feature which with th=
e benefits of typed properties
> could reduce the boilerplate on initializing object and setting their pro=
perties in one expression.
Exactly my motivation with COPA as well;
- Typed properties - check,
- Reduce boilerplate - check,
- Initializing and setting properties in one expression - check.

> With object initializer, this could be reduced to:
>
> $this->dispatch(new SomeCommand { foo =3D 'bar', baz =3D false });
And with COPA it would be;
$this->dispatch((new SomeCommand)->[ foo =3D 'bar', baz =3D false ]);
Subtle differences, when compared to the currently available alternative.

> But as mentioned IMO this is a different feature than what you propose an=
d personally I see no point
> in reducing only assignment statements without combining it with object c=
onstruction for these kinds
> of small objects, DTO's, commands, queries and events.
Maybe you missed that COPA can be combined with object construction?

> but personally I don't need a constructor at all in those cases since we
> have typed properties and it looks like they could be also marked as read=
-only in next major PHP version.
Exactly, and as I couldn't help notice that you voted for the Write
Once Properties RFC, which clearly states that
object construction is a fuzzy term (meaning don't take it too
seriously) and lazy initialization is a feature...

I hope you will either reconsider your support for COPA or let me know
what I'm missing so I can
consider other directions.