Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Rename default method #35
Discussion in #3 yielded the following conclusions as of 2019-11-25:
We are still undecided whether we want to propose additional functionality around parsing UUIDs or outputting them in representations other than strings (e.g. bytes).
@rmg feel free to have a look as well!
Discussion in #3 yielded the following conclusions as of 2019-11-25: - We only want to support v4 UUIDs initially - Exporting them as uuid() might cause confusion should we ever want to support other algoritihms in the future. - Using "v4" in the name seems to cause more confusion than clarification since the whole "Version" terminology in the RFC is pretty confusing per se. - Using the term "random" to describe v4 UUIDs yielded generally positive feedback and other languages/libraries seem to use it as well. - There's general agreement that we should not support algorithms other than v4 random UUIDs for now.
Discussion in #3 showed that there is general agreement for only supporting the v4 algorithm. However, there are concerns that, if we design an API that promotes one algorithm as the default, this assumption might not hold in the future. In order to provide a more future-proof API we may therefore only support certain algorithms, but will likely not treat any of the supported algorithms in a speacial way.