All the code in crypto.go has been cleaned up as well as the related tests.
Still to do is stuff like adding in errors instead of the current status booleans and the goDocs formatting but I can do that in parallel to your code review.
start with 'go test' just to see what the tests are before using the '-debug1' flag.
All the code in crypto.go has been cleaned up as well as the related tests. Still to do is stuff like adding in errors instead of the current status booleans and the goDocs formatting but I can do that in parallel to your code review.
start with 'go test' just to see what the tests are before using the '-debug1' flag.