Added dictionary key support

[zorgoz]

See: #86

[github-actions]

This PR is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[zorgoz]

Is this repo abandoned?

[Vectorial1024]

I have no relationships with CyGames (the owner of this repo), but by cross-referencing with other online sources, I can see the UUID specs now have a spec for UUID v7, which is basically the ULID spec except a few bits are taken away to denote the UUID version (as per usual UUID spec) and the variant.

With this, as more and more systems start to support UUIDv7 (e.g. database engines offering UUID-optimized indexing, existing UUID libraries adopting the UUIDv7, etc), perhaps this "ULID" concept may actually become legacy code.

ULID was created because the UUIDs available back then simply did not have time-based natural sorting, which causes a lot of pain (e.g. extra painful indexing when mass-inserting to the primary key field). My opinion is that, for new systems, perhaps it is better to just use UUIDv7 instead of ULID.

I can see why this package is suddenly "abandoned".

[neuecc]

Regarding Ulid vs UUIDv7, I've mentioned this before, but I'm more positive about adopting UUIDv7.
#85 (comment)
Basically, I think the Ulid specification has served its purpose.

However, thank you for the PR, and sorry for leaving it without a response.
I think this PR itself is useful, so considering the slight behavior change, I'll release it as a minor version update (1.4.0).

[zorgoz]

Thank you. I am using Ulid in a .net 8 project, and heavily relying on the default base32 serialization. So I'll be sticking with it for a while. Yoshifumi Kawai ***@***.***> ezt írta (időpont: 2025. júl. 25., P 12:19):

…

*neuecc* left a comment (Cysharp/Ulid#87) <#87 (comment)> Regarding Ulid vs UUIDv7, I've mentioned this before, but I'm more positive about adopting UUIDv7. #85 (comment) <#85 (comment)> Basically, I think the Ulid specification has served its purpose. However, thank you for the PR, and sorry for leaving it without a response. I think this PR itself is useful, so considering the slight behavior change, I'll release it as a minor version update (1.4.0). — Reply to this email directly, view it on GitHub <#87 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAL7DEV537BP33KTDNPOLOL3KIACNAVCNFSM6AAAAABSGVJUP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJXGIYDMMZVHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>