Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108371
MIME-Version: 1.0
References: <D5ACEB01-4E1E-407A-8441-D8C6E0D36CCA@gmail.com>
In-Reply-To: <D5ACEB01-4E1E-407A-8441-D8C6E0D36CCA@gmail.com>
Date: Tue, 4 Feb 2020 14:10:02 +0100
Message-ID: <CADyq6s+SPJj_aGhg044XbW4KdRNYrV=bAxGX6ioMpihpg0E2SA@mail.gmail.com>
To: Steven Wade <stevenwadejr@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a86421059dbfc2d6"
Subject: Re: [PHP-DEV] [RFC - discussion] __toArray()
From: ocramius@gmail.com (Marco Pivetta)

--000000000000a86421059dbfc2d6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Linking (again) previous discussions:
https://externals.io/message/98539#98539

`__toArray` as a magic function call when `(array)` cast happen is a bad
idea: it is a BC break, and it removes one of the very few interactions
(with objects) that didn't cause any side-effects (
https://externals.io/message/98539#98545,
https://externals.io/message/98539#98567)

Greets,

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


On Tue, Feb 4, 2020 at 2:03 PM Steven Wade <stevenwadejr@gmail.com> wrote:

> Hi all,
>
> I=E2=80=99d like to officially open my __toArray() RFC <
> https://wiki.php.net/rfc/to-array> up to discussion. I=E2=80=99ve delayed
> changing the status until I had more time to respond to the discussion, b=
ut
> since it=E2=80=99s been brought up again <https://externals.io/message/10=
8351>, I
> figured now is the best time.
>
> https://wiki.php.net/rfc/to-array <https://wiki.php.net/rfc/to-array>
>
> Cheers,
>
> Steven Wade

--000000000000a86421059dbfc2d6--