Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78396
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.41 as permitted sender)
Message-ID: <544E81B2.5080107@gmail.com>
Date: Mon, 27 Oct 2014 10:32:34 -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: Lester Caine <lester@lsces.co.uk>, internals@lists.php.net
References: <544DA1CD.9070109@php.net> <544E0AE1.9090406@lsces.co.uk>
In-Reply-To: <544E0AE1.9090406@lsces.co.uk>
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!
> Is the resulting value intended always to return the same object
> independent of what has been done to the object in the mean time? 
That's on you to decide. If you have immutable value object, then yes.
If you have mutable value object (which usually isn't a good idea, but
who knows) then no. If it's not a value object, then probably you don't
want __hash on it at all.

> A fixed 'address' for the physical data when used as an array key? If
> that is the case, then __toKey seems more comfortable. To me a hash is 
I'm fine with __toKey, if that's what seems better to the majority.