Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78387
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <544DA1CD.9070109@php.net>
References: <544DA1CD.9070109@php.net>
Date: Mon, 27 Oct 2014 14:18:02 +0400
Message-ID: <CAEbg-4YmUzuAEJZOqqCC=vJ=XY5b7HCZnj25B_JYxu1XJof_YQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c37c18840473050664d81c
Subject: Re: [PHP-DEV] [RFC] Using objects as keys
From: lisachenko.it@gmail.com (Alexander Lisachenko)

--001a11c37c18840473050664d81c
Content-Type: text/plain; charset=UTF-8

Hello, internals!

> The name __hash is not final, I am open to using __toKey instead or any
> reasonable alternative, we may also include a couple of options in the
> vote if that will be a point of disagreement.

I like this idea with custom hash implementation because spl_object_hash()
is not reliable when objects are quickly created/destroyed, so hashes can
be the same for several different objects. However, will it be better to
introduce an interface for that? For example, Hashable can be a good name
(like Traversable one). Default implementation then can be a simple trait
that will be added later to the concrete class.

--001a11c37c18840473050664d81c--