refactor: noasm to purego #989
Description
Is there a good reason to use the noasm tag in this project contrary to adapting the build tag purego? As I see it, they both mean the same thing or am I confusing concepts here?
The Golang Standard Library utilizes this build tags for e.g. generic cryptography implementations.
It might be a good idea to adjust this project's build tags to the widely adopted scheme.