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.