Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113355
MIME-Version: 1.0
References: <CAF+90c-HY-0fx+pTmntRJZKcQcZFfk3uJwrZ6FAMAx5_Wj+JHw@mail.gmail.com>
In-Reply-To: <CAF+90c-HY-0fx+pTmntRJZKcQcZFfk3uJwrZ6FAMAx5_Wj+JHw@mail.gmail.com>
Date: Wed, 3 Mar 2021 19:25:32 +0100
Message-ID: <CAEPJdu=jpUu7jJoVApn1uwmU-DfsL=WNuVqNTaF2pT2yOUfqow@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000097e80405bca5fab4"
Subject: Re: [PHP-DEV] [RFC] New in initializers
From: kontakt@beberlei.de (Benjamin Eberlei)

--00000000000097e80405bca5fab4
Content-Type: text/plain; charset="UTF-8"

This is

On Wed, Mar 3, 2021 at 4:04 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I would like to propose allowing the use of "new" inside various
> initializer expressions: https://wiki.php.net/rfc/new_in_initializers
>
> In particular, this allows specifying object default values for properties
> and parameters, and allows the use of objects as attribute arguments.
>

This is the missing puzzle piece that i imagined would be needed for nested
attributes. This is really awesome!

I look forward to going over the patch to see how it works, specially since
Martin's and my attempts failed to break through last year for Attributes :)


> The RFC is narrow in scope in that it only adds support for "new". An
> extension to other call kinds should be straightforward though.
>
> Regards,
> Nikita
>

--00000000000097e80405bca5fab4--