Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109120
MIME-Version: 1.0
References: <CAJmjfvW8b=jYTjLfW9N9FT_eQVS7RBe768NZXv-g4V2RM3OgtA@mail.gmail.com>
 <CALKiJKqEbBY3vSFZ5uJoYQ-um0yiR5USgFSo6A6L5Z4Y7SOA2w@mail.gmail.com>
 <CAJmjfvXYpaGx=UfaKN-SA6gYx_Ya22E99AUydBuD=OHWTfcC4A@mail.gmail.com> <CALKiJKqaTonoSEDQdePXB-N+LRQw+34v6i64Pe7vi9+ofDdR5A@mail.gmail.com>
In-Reply-To: <CALKiJKqaTonoSEDQdePXB-N+LRQw+34v6i64Pe7vi9+ofDdR5A@mail.gmail.com>
Date: Tue, 17 Mar 2020 21:57:17 -0500
Message-ID: <CAJmjfvUPgGfZTas4On-DT6JHnFDMAdECgMf=bj1mUDaDoJwWNA@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Compact Object Property Assignment
From: jakob@givoni.dk (Jakob Givoni)

On Tue, Mar 17, 2020 at 9:31 AM Rowan Tommins <rowan.collins@gmail.com> wrote:
> Hm, I see, that does reduce the boilerplate somewhat, although it's still
> split across two classes, and probably therefore two files, which is not
> great.
As an alternative to passive associative arrays, it's a small price to pay for
splitting concerns and having a documented signature for the data structure.
Named parameters is another alternative (unfortunately outside reach for now)
that would work great for a limited number of arguments. COPA does not
make named parameters obsolete, but works great for any number of arguments.

> You're missing some code in your example, though, because you've documented
> one of the options as optional, implying the others should be mandatory; in
> which case you need something like this in the constructor:
I've rewritten parts of the RFC and some examples substantially,
and added your view of mandatory arguments in the "Open Issues" section.

> It might be interesting to have the syntax run before the constructor
> rather than after, or trigger some other magic method which could do
> tidying and validation, so it could apply to more circumstances.
Hmmm, in the Write Once Properties RFC they seem to believe
that object construction is a "fuzzy" term and that lazy initialization
is a feature.

We can add better 'automagic' support for mandatory arguments,
filtering and validation
in incremental proposals, to avoid biting off more than we can chew, but we
have to start somewhere.