Go reflection reads compile-time type metadata at runtime
The post shows that Go’s reflect package doesn’t generate type info on the fly – it simply dereferences the metadata the compiler baked into the binary. By tracing TypeOf and ValueOf down to a single pointer load, it reveals why reflection is cheap enough for practical use and how you can reason about its limits.