What are the pitfalls of Golang?

This article is to share with you about the contents of the Golang pit. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Https://i6448038.github.io/2017/07/28/GolangDetails/

New (type) is not nil

Fmt.Println (new (int) = = nil) # false

Var I * int

Fmt.Println (i==nil) # true

There can be multiple init functions in a package, and the calling order of multiple init functions https://golang.org/ref/spec#Program_initialization_and_execution

Guess what the output of the following code is?

Package main

Import "fmt" import "strconv" func main () {div,_: = strconv.ParseFloat ("0", 64) a: = 37.2-float64 (int (3/div)) * 150 x:=fmt.Sprintf ("% f", a) fmt.Println (x) / / 1383505805528216371200.000000} Thank you for reading! This is the end of this article on "what are the pitfalls of Golang?". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!