You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
1\$\begingroup\$ @JonathanAllan yes I have, will post the collision check soon \$\endgroup\$Surculose Sputum– Surculose Sputum2020年03月09日 03:09:51 +00:00Commented Mar 9, 2020 at 3:09
-
\$\begingroup\$ Snap! Will do, thanks for pointing it out. \$\endgroup\$Surculose Sputum– Surculose Sputum2020年03月09日 03:32:38 +00:00Commented Mar 9, 2020 at 3:32
-
1\$\begingroup\$ If the hash is indeed 64 bits and roughly random, it seems very likely it will give no false matches with two-character changes, but a check would indeed be good. \$\endgroup\$xnor– xnor2020年03月09日 03:34:10 +00:00Commented Mar 9, 2020 at 3:34
-
1\$\begingroup\$ @JonathanAllan took a long time, but I checked and all inputs return the correct output. \$\endgroup\$Surculose Sputum– Surculose Sputum2020年03月09日 04:28:13 +00:00Commented Mar 9, 2020 at 4:28
-
1\$\begingroup\$ Assuming sufficiently high recursion limit and stack size, you can write it as a recursive function for 98 bytes. Can't show examples in this TiO link, because it will exceed the character limit of this comment. \$\endgroup\$Jitse– Jitse2020年03月09日 10:23:32 +00:00Commented Mar 9, 2020 at 10:23