Revision 653b1f9ada2fb9c7b2189f41fa277fc55c7eab0c authored by Antoine R. Dumont (@ardumont) on 06 August 2020, 10:55:23 UTC, committed by Antoine R. Dumont (@ardumont) on 06 August 2020, 16:50:27 UTC
The existing implementation computed the next token using the tok (adding 1).
It's not good enough as it would skip some contents in case of collision on
tok (collisions exist as the tok here is a noncryptographic hash on 32 bits).

Related to T2518
1 parent be9e958
Raw File
CONTRIBUTORS
Daniele Serafini
Ishan Bhanuka
Quentin Campos
back to top