> I just started the voting for the inclusion of a UUID value object in
> PHP's core, targeting PHP 7.3. I wanted to start earlier, but was sick
> the whole week.
> The voting is open starting now and until September 16. (2 weeks).
IMHO, the RFC misses its own point. The introduction claims that
uniqid() is insufficient, and that UUIDs are much more appropriate. I
fully agree. However, instead of providing a single function to replace
uniqid() it offers a full blown class which even includes *parsing* of
UUIDs. The RFC furthermore claims:
| A programming languageâs standard module should provide the most basic
| and repeating building blocks, to ensure that developers can achieve
| things fast without much hassle.
I fully agree, but I don't see that *parsing* of UUIDs is such a most
basic building block, and even most of the rest of the proposed UUID
class doesn't appear to fit that category.
With regard to type-safety (which is probably the point of parse()):
having type-safe UUIDs is only a fraction of one percent of what is
occasionally needed in applications â do we really want to add thousands
of classes to ext/standard?
Christoph M. Becker