When working in go1.20 I ran into crypto mathematics that failed because uint is using *. The math overflowed the JS int causing it to switch to using an exponent and dropping the LSBs. Crypto needs those LSBs and expected the value to rollover. Using $imul instead of * fixes this problem. Since uint is equivalent to uint32 in GopherJS and int32, uintptr, uint32, and int were already using $imul I figured that uint should probably be using it too.

GopherJS emulates a 32-bit environment. This means that int, uint and uintptr have a precision of 32 bits.

Even though this issue was discovered while working on go1.20, the fix isn't specifically related to go1.20. This should help anyone using master and also expecting uint to rollover the same as uint32.