Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109083
MIME-Version: 1.0
References: <CAJmjfvW8b=jYTjLfW9N9FT_eQVS7RBe768NZXv-g4V2RM3OgtA@mail.gmail.com>
 <CAKuGYLStcuLqpRu+tz2dSGRU5RCxhkDUFZ7eNZhQxGDzBbvx9g@mail.gmail.com>
In-Reply-To: <CAKuGYLStcuLqpRu+tz2dSGRU5RCxhkDUFZ7eNZhQxGDzBbvx9g@mail.gmail.com>
Date: Mon, 16 Mar 2020 20:13:27 -0500
Message-ID: <CAJmjfvX_GhMuYYMg2zzFncsDAeyJhOTTsJ_98rj3SpMFGO1xqQ@mail.gmail.com>
To: Matthew Brown <matthewmatthew@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)

On Mon, Mar 16, 2020 at 9:10 AM Matthew Brown <matthewmatthew@gmail.com> wr=
ote:
> I love the idea!
Thanks Matthew!

> The syntax for new objects looks a little verbose =E2=80=93 would it be p=
ossible to use
>
> $foo =3D new Foo()[
>   property1 =3D "hello",
>   property2 =3D 5,
> ];
The short answer: I don't think so.

This is not possible (though it's arguably 'nicer'):

new Foo()->doSomething(); // syntax error, unexpected '->'

Not sure why, but it's necessary to wrap the instantiation in brackets:

(new Foo())->doSomething(); // Ok

If someone can explain why, it would be enlightening!

Furthermore, dropping the arrow would create conflicting syntax with
array access:

$foo[1]; // Array access, give me the element with index 1, can be
used on objects as well
$foo[a =3D 1]; // Property assignment... ???

I'll update the RFC to reflect your proposal.

Thank you,
Jakob