Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104195
MIME-Version: 1.0
References: <CAHE1Edvdo3qhOvJopP5fxsWZCuDAw8PZ5AXNy4=--bWK7_6T=w@mail.gmail.com>
In-Reply-To: <CAHE1Edvdo3qhOvJopP5fxsWZCuDAw8PZ5AXNy4=--bWK7_6T=w@mail.gmail.com>
Date: Tue, 5 Feb 2019 09:39:20 -0700
Message-ID: <CAFMT4NrMexgvB-g7GoFECRjU-tyEh81J5y5YfnbM-KuTDzZ6aw@mail.gmail.com>
To: Craig Duncan <php@duncanc.co.uk>
Cc: Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [VOTE] Making stdClass iterable
From: levim@php.net (Levi Morrison)

On Mon, Feb 4, 2019 at 11:58 AM Craig Duncan <php@duncanc.co.uk> wrote:
>
> Hi all,
>
> Following the discussion it's now time to vote on whether we make the
> stdClass iterable or not.
> https://wiki.php.net/rfc/iterable-stdclass
>
> Note that while there is an implementation available, the vote is only on
> whether stdClass should fulfil the Traversable interface or not.
> Nikita had some ideas on a different implementation that I'll revisit if
> the vote passes.
>
> Voting will end in two weeks on 2019-02-18
>
> Thanks to everybody that shared their opinion and raised concerns during
> the discussion.
>
> Craig

I just wanted to pipe in to suggest an alternative approach to
accomplish some of the same goals: an external PropertyIterator.

  - It could allow us to refine which property visibilities we care to
iterate over. For instance, if we are in a protected or private
context we may want to still only iterate over public properties.
  - I think that with typed properties we will see more data-only
classes which would benefit from an external PropertyIterator.

Of course, that still means `stdClass` isn't automatically `iterable`,
but if you want it to be then you can pass in a PropertyIterator
instead.