[go-nuts] Some best practices for debuging and optimizing with -gcflags?

What are some best practices for general purpose -gcflags to use for debugging and conversely for optimizing code? -- 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 t

[go-nuts] Why does my program hang?

package main import ( "fmt" "os" "strconv" "crypto/rand" "math/big" "unicode" "unsafe" ) func main() { num, err := strconv.ParseUint(os.Args[1],10,64) if err != nil { panic(err) } randrunes := make([]rune,num,num) var char rune for i :=

[go-nuts] Why is Errorf() in the fmt packages and not in the errors package?

The title. -- 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.