Go enjoyer paradox: liking the fact that there will never be a Go v2, and disliking the fact that there will never be a Go v2 with nil-safety.
Go enjoyer paradox: liking the fact that there will never be a Go v2, and disliking the fact that there will never be a Go v2 with nil-safety.
You can simply use the fieldalignment tool and do it manually. pkg.go.dev/golang.org/x...
You can simply use the fieldalignment tool and do it manually. pkg.go.dev/golang.org/x...
Same question could be asked for github.com/google/go-cmp why it was never adopted in std lib.
Same question could be asked for github.com/google/go-cmp why it was never adopted in std lib.
My favourite way to deploy Go backend is through fly.io. They have decent Go documentation and a fair free tier if you stay under a certain usage limit.
My favourite way to deploy Go backend is through fly.io. They have decent Go documentation and a fair free tier if you stay under a certain usage limit.
Whick platforms do you target? Have you tried wasm?
Whick platforms do you target? Have you tried wasm?
How do you conclude Go might get different syntax?
How do you conclude Go might get different syntax?