Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110007
MIME-Version: 1.0
References: <CAF+90c8m-CB3ZxAHeoOJVxJGhysLfZqpz3mq475GPnMEDA6iqQ@mail.gmail.com>
 <CADyq6s+pfDfDey8hGT=zDD5hwyKjq3q6V8xPVyP03z=6MwGgdQ@mail.gmail.com> <d54d3a5f-edf7-4bd3-92ce-f3cdc74631bc@www.fastmail.com>
In-Reply-To: <d54d3a5f-edf7-4bd3-92ce-f3cdc74631bc@www.fastmail.com>
Date: Tue, 5 May 2020 17:38:19 +0200
Message-ID: <CADyq6sKVnHooXmT9eCmXJpju3h6Q_rfao6gT4SdEs+8OVzXBvA@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000086e40a05a4e87012"
Subject: Re: [PHP-DEV] [RFC] Named arguments
From: ocramius@gmail.com (Marco Pivetta)

--00000000000086e40a05a4e87012
Content-Type: text/plain; charset="UTF-8"

Hey Larry,


On Tue, May 5, 2020 at 5:29 PM Larry Garfield <larry@garfieldtech.com>
wrote:

> The biggest use case I see is, as discussed previously, value object
> constructors.  "Pass an entirely untyped and undocumentable array of
> parameters" is not an sufficient userland solution in my mind, but is the
> only available alternative right now.
>

This is easily mitigated by named constructors (
https://verraes.net/2014/06/named-constructors-in-php/), which are a
good/established practice among those using value objects.

You can create multiple (meaningful) constructor signatures depending on
use-case, which is still a much safer approach than delegating this
responsibility to a caller.

My example above uses a `::fromArray()` "factory" precisely for that
purpose.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--00000000000086e40a05a4e87012--