Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125958
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\))
Subject: Re: [PHP-DEV] [Discussion] Make objects unpackable by default
Date: Thu, 14 Nov 2024 13:37:46 +0000
References: <CALWFqqCWV6bzJ0wQud5uH9U82JtNGOqjTOad-w7PVoZ4yn3YVQ@mail.gmail.com>
 <CADyq6s+rctWKjQG2g-sy_tWibdyesLKkuxCwNCyor1_KhBnpaQ@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
In-Reply-To: <CADyq6s+rctWKjQG2g-sy_tWibdyesLKkuxCwNCyor1_KhBnpaQ@mail.gmail.com>
Message-ID: <C62F7404-7472-4A01-BD43-C3C5A667DFC5@cschneid.com>
From: cschneid@cschneid.com (Christian Schneider)

Am 14.11.2024 um 10:59 schrieb Marco Pivetta <ocramius@gmail.com>:
> On Thu, 14 Nov 2024, 11:29 MrMeshok, <ilyaorlov124@gmail.com> wrote:
>> Hello, Internals!
>>=20
>> As you know if you try to unpack a regular object (`...$object`) you =
will get an error: Only arrays and Traversables can be unpacked.
>> I don't really see a reason for this restriction, because foreach on =
objects works perfectly fine, so I made a feature request on GitHub to =
change this behavior (https://github.com/php/php-src/issues/16038) and =
was advised to see opinions on this here.
>> So, what do you think? And does this change require RFC?
>=20
> TBH, foreach on objects is already quite an abomination in itself =F0=9F=
=98=AC

It is a bit less weird if you use value objects or json data in object =
form.
I would be careful to judge how other people use the language, just =
saying ;-)

- Chris