Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114984
MIME-Version: 1.0
References: <DM6PR07MB66186AD1AF40B256C5C3ABA0F90A9@DM6PR07MB6618.namprd07.prod.outlook.com>
 <7f2da982-e29b-ccca-bddc-24ae7f4b0390@gmail.com>
In-Reply-To: <7f2da982-e29b-ccca-bddc-24ae7f4b0390@gmail.com>
Date: Mon, 21 Jun 2021 18:49:51 +0100
Message-ID: <CAGBsUrcc-ujQwo0h+rx8H9ScvBLawkrn66q2rLvB4BfpJfwZdQ@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007adfe705c54a4d13"
Subject: Re: [PHP-DEV] [PROPOSAL] Bare name array literals (again)
From: tekiela246@gmail.com (Kamil Tekiela)

--0000000000007adfe705c54a4d13
Content-Type: text/plain; charset="UTF-8"

Hi Tyson,

Interesting proposal, but I was going to reply with the exact same response
as Rowan. Why not use DTOs for such purposes? Arrays have rather limited
use cases. If you need to return multiple results from a function then you
should return an object with typed properties.
I don't like the idea of adding yet another syntax for creating arrays,
especially one with limitations. If your array keys contain spaces or
special characters then you need to use the current syntax. Adding to the
fact that arrays have no type safety, I don't see much use for the newly
proposed syntax.

I would prefer an improved syntax for creation of anonymous objects. This
is something which I have been annoyed with, myself.I'd like to see a
simple way of creating anonymous objects with typed properties.

Regards,
Kamil

--0000000000007adfe705c54a4d13--