Open jmventura opened 6 years ago
+1
If you just want uint64 to represent 32-bit epochs, you're probably fine. If you want to move to sub-second resolution with uint64 nanoseconds, then there are more patches required to support larger actual timestamp sizes.
Also, not sure how to solve this without breaking anybody using this code. Perhaps a tsz (32-bit) and tsz64 types generated from the same base implementation.
@dgryski: Have you seen my fork?
Hi there, are you planning to implement uint64 timestamps as described in the Facebook's paper anytime soon?
Thanks for the great contribution!