Enum instances aren't singletons

[hikari-no-yume]

Ideally, SomeEnum::Foo() should always return the same instance of SomeEnum, so you can do $someEnumValue1 === SomeEnum::Foo() instead of $someEnumValue1->getValue() !== SomeEnum::Foo

[mnapoli]

Yes that's really something I'd like to have!

Maybe a 2.0 version could make the constructor private? Currently there is a "cache" so that MyEnum::FOO() always returns the same object, the only problem is that users can still do new MyEnum(MyEnum::FOO)…

But then what about deserialized enums…

[hikari-no-yume]

Oh, deserialisation would be an issue :/

Also, I discovered that I may just be able to use == as it does structural comparison.

[mnapoli]

yep forgot to mention that, I use == too.

[adrium]

See #43 or adrium/php-enum version 1.5.1

[shadowhand]

What would be the point of singletons? Enums are value objects and value objects equality is not based on identity:

a value object is a small object that represents a simple entity whose equality is not based on identity

The current implementation of Enum is correct because it contains an equals() method that tests equality based on type and value.

[mnapoli]

@shadowhand that's a good point indeed. I think the main "issues" would be practicality (ability to use ===) and performances.

But this package has worked fine until now without singletons, a 2.0 would create a lot of conflicts downstream for very little gain so I think it's acceptable to keep this on hold unless we find a very good reason to release a v2.0.

[KartaviK]

Constructor is public, so it will automatically create new instance.
To use singletons, you can use search method, like this:

$singletone = MyEnum::{MyEnum::search($value)}();

Not best practice, but it will always create single instance

[shadowhand]

@KartaviK see my response above. Enums (as implemented in this package) are value objects, and value objects have equality by state, not by being singletons.

[dbalabka]

Creating a new object for each enum usage is memory wasting. Imagine you are fetching a huge amount of rows from the database. High memory usage affects performance in general (e.g. GC).

Comparing the other languages implementations you can see that they use the singletons:

1. Python https://repl.it/@torinaki/Python-Enum-is-Singleton
2. Java https://repl.it/@torinaki/Java-Enum-is-Singleton

[githoober]

What would be the point of singletons? Enums are value objects and value objects equality is not based on identity:

a value object is a small object that represents a simple entity whose equality is not based on identity

The current implementation of Enum is correct because it contains an equals() method that tests equality based on type and value.

IMO, the way this library instantiates its enum values is a detail of implementation. If you disagree, then this library should clearly state in its description that it relies on the value object definition of object equality.

[dbalabka]

I support @githoober. IMO it leads to misunderstanding. Enums and ValueObjects behave differently. Enums (as I showed in a comment above) in most languages represents the set of constants. In turn, ValueObject is a structure that can be instantiated (!) with any set of values for defined parameters.