Hope we remove the annotation ExperimentalUuidApi soon and getting a stable version (it's stable already), we've been using it in prod without any issue, API surface is good, great experience so far.
Comments
Log in with your Bluesky account to leave a comment
Thank you for sharing the links!
I agree with KEEP and plan to use v4 for basic UUIDs in the initial release.
However, as highlighted here, I frequently use time-based v7 UUIDs to optimize database performance. I hope it gets implemented soon! https://uuid7.com/
Yeah, time-based is mentioned there as well, for now it seems out of scope for the Standard Library because of how complex it is to handle correctly across platforms.
But other libraries (like database libraries) can generate them and reuse the same Uuid type in their API.
Comments
And you can also check the related discussion for even more:
https://github.com/Kotlin/KEEP/issues/382
I agree with KEEP and plan to use v4 for basic UUIDs in the initial release.
However, as highlighted here, I frequently use time-based v7 UUIDs to optimize database performance. I hope it gets implemented soon!
https://uuid7.com/
But other libraries (like database libraries) can generate them and reuse the same Uuid type in their API.