Has the underlying structure of slice changed in Go 1.20?

Go version 1.20: Major adjustments to the underlying structure of Slice

The Slice structure in the Go language has always attracted much attention. This article will explore the significant changes in the underlying structure of Slice in Go 1.20. Previously, the reflect.sliceheader structure was the underlying implementation of Slice. However, Go 1.20 has adjusted this.

Source code analysis shows that reflect.sliceheader and reflect.stringheader have been deprecated, instead being a new structure based on unsafe.pointer pointer. This change enhances security and prevents the Garbage Collecting Mechanism (GC) from accidentally recycling underlying data.

The source code comments clearly state:

 // deprecated: use unsafe.slice or unsafe.slicedata instead.
type sliceheader struct {
    ...
}

The new Slice structure is defined as follows:

 // Unlike reflect.SliceHeader, its Data field is sufficient to guarantee the
// data it references will not be garbage collected.
type Slice struct {
    ...
}

The official Go document also mentions slicedata , string and stringdata functions added to the unsafe package. These functions work in conjunction with the slice function in Go 1.17, providing more complete Slice and string value building and parsing capabilities without relying on their precise underlying representation.

The issue with the search results of the official GitHub repository code of Go is empty, which may be caused by search function settings or permission restrictions.

In short, Go 1.20 has made important updates to the underlying structure of Slice, adopting a safer unsafe.pointer type, and providing new functions to facilitate developers to manipulate Slice and strings more efficiently. This change improves security and simplifies underlying operations.

The above is the detailed content of Has the underlying structure of slice changed in Go 1.20?. For more information, please follow other related articles on the PHP Chinese website!