Go Slices: `var` or `make` – Which Declaration is Best?
Declaring a Portion: var or make?
In Go, portions are an essential data structure. However, there are two different ways to declare a portion:
var s []int
This declaration creates a worthless portion, that is, a portion that does not stores any element. The reference value of s is nil.
s := make([]int, 0)
This statement creates an empty slice, that is, a slice with zero elements but with allocated memory. The reference value of s is not nil.
What's the Difference?
The main difference between these two declarations is that var declares a valueless portion while which make allocates memory for an empty chunk. Using var creates a chunk that initially has no storage space allocated to it. No elements can be stored in the slice until memory is allocated to it.
On the other hand, make allocates memory for an empty slice, which means that elements can be stored in it immediately. However, the initial portion size is zero, so it is important to increase the portion size if more items are to be stored.
What is the Best Option?
It is generally recommended to use var to declare a portion if you do not know the exact size of the portion to be used. This allows the slice to grow and resize dynamically as needed.
If the exact size of the slice is known, using make can be more efficient, as it allocates memory immediately and avoids overloading the slice. creation of a worthless portion.
The above is the detailed content of Go Slices: `var` or `make` – Which Declaration is Best?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

What should I do if the custom structure labels in GoLand are not displayed? When using GoLand for Go language development, many developers will encounter custom structure tags...
