The fact that collisions are possible does not make them "easy to create" especially when you add the compileable requirement. If you're uneasy about md5 you could always use more bits - like SHA1 used by "git" or SHA256 (or larger) if you're really paranoid.
On Wednesday, August 3, 2016 at 1:14:53 PM UTC-4, atd...@gmail.com wrote: > > Would a md5 hash suffice? > > I mean, it is probably easy to create collisions, but the source still > needs to compile so... > > Or an md5 hash and using go/types to make sure that any object escaping > the package boundaries is still present and none other have been added. > > Any idea? > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
