`make([]int, 0)` vs. `[]int{}`: What's the Best Way to Initialize an Empty Slice in Go?

Best Practice for Initializing Empty Slices

In Go, creating an empty slice with a non-fixed size can be achieved using two methods:

• make([]int, 0)
• []int{}

Which approach is considered the correct way depends on the following factors:

Semantic Equivalence:

Both methods result in an empty slice. They are semantically identical and will behave the same way in most scenarios.

Internal Implementation:

• make() function: Makes an internal call to the runtime to create the slice.
• []{} syntax: Creates a composite literal, implicitly invoking make() under the hood.

Performance:

None of the above options involve any allocation. So, there is no performance difference between them.

Other Options:

You can also declare an empty slice using a nil value:

• var myslice []int

However, note that a nil slice is functionally equivalent to an empty slice, but it points to nothing.

JSON Marshaling:

• Nil slice: Marshals into "null"
• Empty slice: Marshals into "[]"

Ultimately, the choice between make() and []{} is primarily a matter of preference. However, it's important to be aware of the differences in internal implementation when choosing between the two options.

The above is the detailed content of `make([]int, 0)` vs. `[]int{}`: What's the Best Way to Initialize an Empty Slice in Go?. For more information, please follow other related articles on the PHP Chinese website!