Prev Next

Golang / Golang Internals and Memory Management Interview Questions

How does append() work internally and what triggers a reallocation?

append(s, elems...) adds elements to slice s. The critical behaviour depends on whether the backing array has spare capacity:

  • If len(s) + len(elems) <= cap(s): no new allocation. The elements are written directly into the existing backing array beyond s.len. The returned slice shares the same backing array as s but with an incremented len.
  • If capacity is exhausted: Go allocates a new, larger backing array, copies all existing elements, then appends the new ones. The returned slice points to the new array; the original backing array is now unreferenced (and eligible for GC).
s := make([]int, 3, 5) // len=3 cap=5 — room for 2 more
s2 := append(s, 10)    // fits in cap — no reallocation
// s and s2 SHARE the backing array until cap is exceeded

s3 := append(s2, 20, 30) // cap exceeded — new backing array allocated
// s, s2 still point to OLD array; s3 points to NEW array

// ALWAYS use the returned value of append
s = append(s, 99) // wrong to ignore the return — s might be outdated

// Growth strategy (Go 1.18+)
// cap < 256:  double (newcap = oldcap * 2)
// cap >= 256: grow ~25% + smooth correction to avoid thrashing

// Pre-allocate when the final size is known
names := make([]string, 0, 1000) // avoids N reallocations in a loop
for _, n := range rawNames {
    names = append(names, n)
}

The growth strategy changed in Go 1.18 from a simple doubling to a smoother formula: small slices (cap < 256) still double; larger slices grow by about 25% with a correction that blends the doubling and 25% rates. This avoids the cliff-edge behaviour at the transition point.

Hidden sharing trap: if you append to a sub-slice that still has spare capacity, the write goes into the original backing array, silently overwriting data seen by other slices sharing that array. Always use the three-index slice s[lo:hi:hi] to set cap equal to len when you want to guarantee a fresh allocation on the next append.

What happens when append() is called on a slice that has no remaining capacity?
What is the approximate growth factor for a Go slice with capacity below 256 when append triggers reallocation?

Invest now in Acorns!!! 🚀 Join Acorns and get your $5 bonus!

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Earn passively and while sleeping

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.


Webull! Receive free stock by signing up using the link: Webull signup.

More Related questions...

What is the internal structure of a Go slice and how does it differ from an array? How does append() work internally and what triggers a reallocation? When does a variable get allocated on the stack versus the heap in Go? How do goroutine stacks work and how do they grow in Go? How does Go's garbage collector work? Explain the tri-color mark-and-sweep algorithm. What are GOGC and GOMEMLIMIT and how do you use them to tune GC behavior? How are Go maps implemented internally and what does that mean for performance? When should you use sync.Map instead of a mutex-protected regular map? How do pointers work in Go and when should you pass by pointer vs by value? How does Go's goroutine scheduler work? Explain the GMP model. How are Go channels implemented internally? How are Go interfaces implemented internally and why do they matter for performance? How does Go's memory allocator work? Explain mcache, mcentral, and mheap. How are strings represented in Go and why are they immutable? How does defer work internally in Go and what are its performance implications? How do panic and recover work in Go and when should you use them? How do you profile a Go application using pprof? What is the Go race detector and how does it work? What is the difference between sync.Mutex and sync.RWMutex and when do you use each? When should you use channels versus mutexes in Go concurrency? How do generics work in Go 1.18+ and how do they affect performance? How does context.Context work and when do you use each context type? What is the 'unsafe' package in Go and when is it used? What is the nil interface pitfall in Go and how do you avoid it? What are goroutine leaks and how do you detect and prevent them? How does sync.WaitGroup work and what are common mistakes? How do closures capture variables in Go and what is the classic goroutine loop bug? How does struct embedding work in Go and how does it differ from inheritance? How does error wrapping work in Go 1.13+ with errors.Is and errors.As? How do you write and run benchmarks in Go? How does struct field ordering affect memory layout and performance in Go? How do you implement fan-out and fan-in patterns with Go goroutines? How does the reflect package work in Go and when should it be used? What is cgo in Go and what are its performance trade-offs? What does GOMAXPROCS control and how does it affect Go's concurrency model? How does sync.Once work and what are its use cases? What are the most common memory leak patterns in Go and how do you diagnose them? How do build constraints (build tags) work in Go? How do io.Reader and io.Writer work and why are they fundamental to Go's I/O model? What is the Go optimisation workflow? How do you go from a performance problem to a fix? What is sync.Pool and when should you use it? How do type assertions and type switches perform internally in Go? How does Go's module system work and what is the role of go.sum? How do you implement a worker pool in Go? What static analysis tools are essential for a Go project and what does each check?
Show more question and Answers...

GoLang Interfaces and Object Oriented Interview Questions

Comments & Discussions