Simplify make and avoid 0 as second argument

Docs > コード分析 > Static Analysis Rules > Simplify make and avoid 0 as second argument

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

Metadata

ID: go-best-practices/simplify-make

Language: Go

Severity: Info

Category: Best Practices

Description

In Go, developers should avoid using make([]int, 0) and instead use make([]int).

Here are a few reasons why:

Simplicity and clarity: Using make([]int) instead of make([]int, 0) is simpler and clearer in its intent. The make([]int) syntax creates a slice with a length and capacity of 0, indicating an empty slice. It avoids unnecessary redundancy by omitting the explicit specification of a capacity of 0.
Efficiency: The make([]int) expression is more efficient in terms of memory allocation. When creating a slice with a length and capacity of 0, Go’s underlying implementation already handles the allocation and management of an empty slice efficiently. Explicitly specifying a capacity of 0 in make([]int, 0) doesn’t provide any additional benefit in terms of performance.
Readability and maintainability: Code using make([]int) is easier to read and maintain because it represents the intent of creating an empty slice explicitly. It aligns with the idiomatic Go style and is widely recognized and understood by the Go community.

In summary, it is recommended to use make([]int) when creating an empty slice in Go instead of make([]int, 0). This approach simplifies the code, improves its readability, and ensures efficient memory allocation.

Non-Compliant Code Examples

func main () {
    foo := make([]int, 0, 0)
    foo := make(map[string]string, 0)
}

Compliant Code Examples

func main () {
    foo := make([]int, 0)
}