use `u128` instead of `(u64, u64)` as byte level representation
dylanhart opened this issue · comments
Using a u128 primitive will lead to a simpler and maybe faster implementation. The only problem is that this is currently a nightly feature, so u128 support will have to be implemented after it hits stable. This is a breaking API change due to the Ulid tuple constructor.
Fixed in 932e950