Can a pointer point to both the stack and the heap?

Yes, a pointer in Go can point to both stack memory and heap memory.

In Go, the compiler and runtime decide where to allocate objects—on the stack or on the heap—based on escape analysis.

If an object only lives within a function and does not escape it, it is usually allocated on the stack. If the object needs to live longer (for example, returned from a function or stored in a closure), it is allocated on the heap, and the pointer will point to the heap.

Thus, a pointer is simply an address in memory, and it can point to different areas depending on where the object resides.

Example:

func foo() *int {
    x := 42 // may be on the stack
    return &x // if x "escapes" the function, the compiler will allocate it on the heap
}

func main() {
    p := foo() // p points to heap memory
    fmt.Println(*p)
}

Here, p points to an area of memory allocated on the heap, even though x is declared within the function.