Prev Next

Golang / Golang Internals and Memory Management Interview Questions

What is the nil interface pitfall in Go and how do you avoid it?

One of Go's most confusing bugs: a nil pointer of a concrete type, when assigned to an interface, produces a non-nil interface value. This breaks code that checks if err != nil — the check passes even though the underlying value is nil.

type MyError struct{ code int }
func (e *MyError) Error() string { return fmt.Sprintf("error %d", e.code) }

// Bug: returns a non-nil interface holding a nil *MyError
func riskyOp(fail bool) error {
    var err *MyError // nil *MyError pointer
    if fail {
        err = &MyError{code: 42}
    }
    return err // WRONG: even when fail=false, the returned error is NOT nil
              // The interface has {type=*MyError, data=nil}
}

e := riskyOp(false)
if e != nil {
    fmt.Println("ERROR:", e) // This PRINTS — interface is non-nil!
}

// Fix 1: return untyped nil when there is no error
func safeOp(fail bool) error {
    if fail {
        return &MyError{code: 42}
    }
    return nil // nil interface — both type and data are nil
}

// Fix 2: use a concrete return type if the caller always knows the type
func safeOp2(fail bool) *MyError {
    if fail { return &MyError{code: 42} }
    return nil // now nil really means nil
}

// Detect with reflect if debugging:
fmt.Println(e == nil)                   // false (interface non-nil)
fmt.Println(reflect.ValueOf(e).IsNil()) // true  (data pointer is nil)

The rule: never return a typed nil as an interface return type. If your function returns an interface (like error), always return the bare nil keyword on the success path, not a nil pointer of a concrete type. The errors.Is and errors.As functions from Go 1.13+ are also affected — they work correctly because they unwrap the interface, but the initial != nil check still fails.

An interface value 'var e error = (*MyError)(nil)' — is e == nil?
What is the correct way to return 'no error' from a function that returns the error interface?

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

Interviews Questions

About Javapedia.net

Javapedia.net is for Java and J2EE developers, technologist and college students who prepare of interview. Also this site includes many practical examples.

This site is developed using J2EE technologies by Steve Antony, a senior Developer/lead at one of the logistics based company.

Follow Javapedia updates

contact: javatutorials2016[at]gmail[dot]com

Kindly consider donating for maintaining this website. Thanks.

Copyright © 2026, javapedia.net, all rights reserved. · .

DMCA.com Protection Status