Hashing Golang Types with AES Instructions

That's clean modern Go.

Doesn't seem very complex, but I'm unclear the reasoning for some things....

I'm not clear, and wondering why, it has to use unsafe pointers? Is it because the hashed types get pushed to the stack?