Description:
------------
The class name produced by `get_class()` on an anonymous class can return the same value for two different anonymous classes, apparently when the `new class` is on the same line (e.g. a function/method call returns a new anonymous class). While the name produced by get_class is documented as "an implementation detail, which should not be relied upon", the behavior that comes as a result is neither documented nor expected: static properties end up having global naming collisions

This can result in weird downstream behavior where static methods defined in the anonymous class can "overlap", and only the most recent definition actually has certain data accessible.

A possible workaround could include the old-fashioned eval-based dynamic definition (like PHPUnit Mock Objects does), but this should not be necessary, and may not be accessible in some environments due to restrictions on eval use.

Test script:
---------------
https://3v4l.org/ZSoeI

Expected result:
----------------
Anonymous classes are completely independent of each other; their identifying information (e.g. generated class name) are not dependent entirely on the point of definition, and their static properties are in no way interrelated.

Also acceptable, though far less desirable: this behavior is documented as something to be expected, with a workaround for this use case suggested.

Actual result:
--------------
If two anonymous classes are generated from the same code, their internal names (get_class()) collide and as such they end up exhibiting some singleton-like behavior.