Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78398
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.48 as permitted sender)
Message-ID: <544E8AE4.3040907@gmail.com>
Date: Mon, 27 Oct 2014 11:11:48 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Etienne Kneuss <etienne.kneuss@epfl.ch>
CC: PHP Internals <internals@lists.php.net>
References: <544DA1CD.9070109@php.net> <CACQesk7PV2KYnRWmF6wSKUGaXMjnLgvPKFmcJ0UZQroB5iqEZw@mail.gmail.com>
In-Reply-To: <CACQesk7PV2KYnRWmF6wSKUGaXMjnLgvPKFmcJ0UZQroB5iqEZw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Using objects as keys
From: smalyshev@gmail.com (Stas Malyshev)

Hi!
> As others noted, it also prevents a full-fledged objects-as-key
> implementation in the future.
You do realize to have such implementation we'd need to rewrite our hash
layer completely and also introduce the concept of immutable object,
otherwise changing the object would make the hash completely broken?
Which means it would probably never happen unless PHP engine is
radically rewritten.
>
> In the end it causes issues and brings very little compared to an
> explicit call to convert an object to a key.
Same as __toString obviously is useless as you could just call a method
explicitly.