Desk & Cabinet

Trace one struct through newUser() and watch exactly what lands on the desk (stack frame) versus the filing cabinet (heap) — and what the caller actually gets handed back.

DESK = stack frame CABINET = heap STICKY NOTE = pointer (&u)

Trace

Primary sources: Go FAQ — stack or heap · The Go Language Specification (pointer types, allocation) · Ardan Labs — Language Mechanics on Escape Analysis. Verify any claim here with go build -gcflags=-m on the real code.

One-off simulator, not a saved lesson. Jump around via the rail, flip Pointer vs Value at the branch, and ask me anything still fuzzy — especially about string/slice fields, sync.Pool, or reading real -m output.