A quick guide to the visual rulebook, its memory examples, and the boundaries of the lesson.
What Go pointer and memory concepts are shown?
The board uses & to get a variable address, * to read the value at a pointer address, T for a normal value, and *T for a pointer to T. It also shows copying a value into a new box, two names pointing to the same box, and why *22 is invalid because only pointers can be dereferenced.
How do I use the visual examples?
Tap any rule card to change the live memory map. Watch the address arrow, value box, pointer box, copy box, and explanation note update. Use the reset button in the Live memory map to return to the address example, then compare it with the mini Go example below.
Who is this tool for?
It is for people beginning Go, developers reviewing pointer syntax, and anyone who learns better from a small visual model before reading a larger program. It is useful as a quick teaching or interview-preparation reference.
What does it not replace?
This is a simplified visual lesson, not a Go compiler, debugger, playground, or complete explanation of the Go memory model. It does not execute code or model every detail of stack and heap allocation, escape analysis, garbage collection, races, or unsafe code.
What example should I remember?
Start with a := 22, then p := &a, and fmt.Println(*p) prints 22. The board separates the address stored in p from the value stored in a so you can see why & asks for an address and * follows a pointer to a value.
Does Go Rules save or upload anything?
No. The board does not ask for files, accounts, or server data. Your selected rule is held in this page while it is open and resets when the page is refreshed. No personal code or pointer examples are uploaded by this visualizer.
Related learning
Continue from the memory model into algorithms, backend concepts, and system design.