Escape analysis awareness

I am the Host. This is Go · expert, lesson 1: Escape analysis awareness. Read the teaching and the stills before the checks. The quizzes are open book and test the subject — Go itself — not product rules or layout trivia.

Expert assumes Introductory through Medium. We go deep — no beginner restarts.

The compiler decides stack vs heap via escape analysis. & and interfaces can force heap.

go build -gcflags=-m shows escape decisions.

Fewer allocations often beat micro-instruction tricks.

API shapes influence escape — returning pointers to locals escapes them.

Put Escape analysis awareness in a sentence you could teach a friend: what changes, what stays the same, and what you expect from the still.

Change one dial at a time when you experiment, then re-run. Batch changes invent ghost bugs.

Predict the still on paper before you type. Prediction turns running into confirmation.

Name each token in the still aloud. Hesitation marks the exact gap.

When something fails, read the last error line first. Calm retries beat rewriting everything.

Open-book means the page is a tool. Pick the claim that matches what we traced.

Keep mistaken traces beside corrected ones. The diff is the real lesson.

Label the runtime or toolchain you are using. Boring mismatches still burn evenings.

package main

import "fmt"

func answer() *int {
	n := 42
	return &n
}

func main() {
	fmt.Println(*answer())
}

Sit with that still. Trace it top to bottom. Name each piece. The exercise asks you to match its essence.

If something fails when you try it yourself, change one thing. Read the error. Return to the still. I will not rush you.

That is the lesson. When every quiz and exercise on this page is green, mark it passed. Next lesson when you are ready.