a6e417dc63
Bumps [go.etcd.io/bbolt](https://github.com/etcd-io/bbolt) from 1.3.9 to 1.3.10. - [Release notes](https://github.com/etcd-io/bbolt/releases) - [Commits](https://github.com/etcd-io/bbolt/compare/v1.3.9...v1.3.10) --- updated-dependencies: - dependency-name: go.etcd.io/bbolt dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
28 lines
1.1 KiB
Go
28 lines
1.1 KiB
Go
package bbolt
|
|
|
|
import (
|
|
"unsafe"
|
|
)
|
|
|
|
func unsafeAdd(base unsafe.Pointer, offset uintptr) unsafe.Pointer {
|
|
return unsafe.Pointer(uintptr(base) + offset)
|
|
}
|
|
|
|
func unsafeIndex(base unsafe.Pointer, offset uintptr, elemsz uintptr, n int) unsafe.Pointer {
|
|
return unsafe.Pointer(uintptr(base) + offset + uintptr(n)*elemsz)
|
|
}
|
|
|
|
func unsafeByteSlice(base unsafe.Pointer, offset uintptr, i, j int) []byte {
|
|
// See: https://github.com/golang/go/wiki/cgo#turning-c-arrays-into-go-slices
|
|
//
|
|
// This memory is not allocated from C, but it is unmanaged by Go's
|
|
// garbage collector and should behave similarly, and the compiler
|
|
// should produce similar code. Note that this conversion allows a
|
|
// subslice to begin after the base address, with an optional offset,
|
|
// while the URL above does not cover this case and only slices from
|
|
// index 0. However, the wiki never says that the address must be to
|
|
// the beginning of a C allocation (or even that malloc was used at
|
|
// all), so this is believed to be correct.
|
|
return (*[maxAllocSize]byte)(unsafeAdd(base, offset))[i:j:j]
|
|
}
|