why entry use array instead of golang map for storage

[xiaoshi100086]

I find entry use array for storage in struct segment.
This approach requires the implementation of get, set interfaces and expansion logic.

type segment struct {
        // ...
	slotLens      [256]int32 // The actual length for every slot.
	slotCap       int32      // max number of entry pointers a slot can hold.
	slotsData     []entryPtr // shared by all 256 slots
}

Why not use golang map?

1. golang map has achieved hash and expansion logic
2. if map value is data address offset instead of data pointer, the GC will omit its content.

[coocood]

When this project was created, the Go GC didn't omit map value.

[lovegnep]

map can not solve the problem of hash collisions