Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79708
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <549009EE.7040808@fischer.name>
Date: Tue, 16 Dec 2014 10:52:19 +0000
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <D5013CDA-61F7-467F-B896-F627D8DBA156@ajf.me>
References: <548FEE87.7020602@gmail.com> <549009EE.7040808@fischer.name>
To: Markus Fischer <markus@fischer.name>
Subject: Re: [PHP-DEV] [RFC][VOTE] Objects as Keys
From: ajf@ajf.me (Andrea Faulds)

Hi Markus,

> On 16 Dec 2014, at 10:31, Markus Fischer <markus@fischer.name> wrote:
>=20
> On 16.12.14 09:34, Stanislav Malyshev wrote:
>> I'd like to initiate a vote on "objects as keys" RFC:
>> https://wiki.php.net/rfc/objkey
>=20
> Am I right this only covers the transformation into the array. Once =
it's
> in it's essential a array compatible key entity (string/integer) so =
when
> you var_dump($array) you only get the values of a hash.
>=20
> In other words: it would not be possible to actually get the object =
from
> the key, just this string/integer which is supposed to reference it?

Exactly. If I were to do this:

    <?php
    class Foo {
        public $foo;
        function __construct($foo) {
            $this->foo =3D $foo;
        }
        function __toKey() {
            return $this->foo;
        }
    }
    $arr =3D [];
    $arr[] =3D new Foo(1);
    var_dump($arr);

I would get this:

    array(1) {
      [0]=3D>
      int(1)
    }

This is the main problem with the RFC: magic, implicit, one-way data =
loss (object to integer/string).

I was previously in favour of this, but it=E2=80=99d prevent actual =
indexing by objects in future, and I can=E2=80=99t think of any use =
cases which aren=E2=80=99t better solved by explicitly converting to a =
string/integer.

Thanks.
--
Andrea Faulds
http://ajf.me/