100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace

Go Reflection Cheat Sheet

Go Reflection Cheat Sheet

Using reflect.Type and reflect.Value to inspect and mutate values at runtime, plus struct tag parsing for encoders and ORMs.

2 PagesAdvancedMar 2, 2026

Type and Value

reflect.TypeOf and reflect.ValueOf are the two entry points into the reflection API.

go
import "reflect"x := 42t := reflect.TypeOf(x)     // reflect.Type: intv := reflect.ValueOf(x)     // reflect.Value wrapping 42fmt.Println(t.Kind())        // reflect.Intfmt.Println(t.Name())         // "int"fmt.Println(v.Int())           // 42 (typed accessor, panics if Kind != Int)// Kind is the underlying category (Struct, Slice, Ptr, Int, ...)// Type can differ from Kind for named types, e.g. type MyInt int has Kind() == Int

Inspecting Struct Fields

Iterate fields, read tags, and get/set values via reflection.

go
type User struct {    Name string `json:"name" validate:"required"`    Age  int    `json:"age"`}u := User{Name: "Alice", Age: 30}t := reflect.TypeOf(u)v := reflect.ValueOf(u)for i := 0; i < t.NumField(); i++ {    field := t.Field(i)    value := v.Field(i)    tag := field.Tag.Get("json")    fmt.Printf("%s (%s) = %v, json tag=%q\n", field.Name, field.Type, value, tag)}

Mutating Values (Requires a Pointer)

You can only Set through an addressable, settable Value — pass a pointer and call Elem().

go
func setName(u *User, name string) {    v := reflect.ValueOf(u).Elem()   // dereference the pointer to get settable Value    field := v.FieldByName("Name")    if field.IsValid() && field.CanSet() {        field.SetString(name)    }}u := &User{Name: "Bob"}setName(u, "Robert")fmt.Println(u.Name)   // "Robert"// reflect.ValueOf(someNonPointer).Elem() panics -- Elem() needs a Ptr or Interface Kind

Calling Functions Dynamically

reflect.Value.Call invokes a function found via reflection, e.g. for plugin systems.

go
func add(a, b int) int { return a + b }fn := reflect.ValueOf(add)args := []reflect.Value{reflect.ValueOf(3), reflect.ValueOf(4)}result := fn.Call(args)          // []reflect.Valuefmt.Println(result[0].Int())      // 7// Checking a value implements an interfacevar w io.Writert := reflect.TypeOf(os.Stdout)fmt.Println(t.Implements(reflect.TypeOf(&w).Elem()))

Key reflect Concepts

Terminology that trips people up when starting with reflection.

  • reflect.Type- static type description: name, kind, methods, fields
  • reflect.Value- a boxed runtime value you can inspect/set/call
  • Kind()- the underlying category (Struct, Slice, Map, Ptr, Int, Func...)
  • Elem()- dereferences a Ptr/Interface Value or gets element type of Slice/Array/Map
  • CanSet()- true only for values obtained via an addressable pointer's Elem()
  • StructTag- raw tag string on a field, parsed with .Get("key")

Constructing Values with reflect.New

reflect.New(t) allocates a zero value of type t and returns a settable *T-shaped Value, the reflective equivalent of new(T).

go
t := reflect.TypeOf(User{})ptrVal := reflect.New(t)          // reflect.Value wrapping *User, addressableelem := ptrVal.Elem()               // dereference to the settable User valueelem.FieldByName("Name").SetString("Grace")elem.FieldByName("Age").SetInt(29)user := ptrVal.Interface().(*User) // recover a real *User to use normallyfmt.Println(*user)                  // {Grace 29}// reflect.Zero(t) gives a non-addressable zero Value without allocation --// useful for comparisons, not for building up mutable structs.

Calling Methods Dynamically

Value.MethodByName and Type.NumMethod enumerate and invoke a value's method set at runtime, e.g. for plugin/RPC dispatch.

go
type Greeter struct{ Name string }func (g Greeter) Greet(prefix string) string {    return prefix + ", " + g.Name}g := Greeter{Name: "Ada"}v := reflect.ValueOf(g)t := reflect.TypeOf(g)for i := 0; i < t.NumMethod(); i++ {    fmt.Println(t.Method(i).Name) // "Greet"}method := v.MethodByName("Greet")if method.IsValid() {    out := method.Call([]reflect.Value{reflect.ValueOf("Hello")})    fmt.Println(out[0].String()) // "Hello, Ada"}

Recursive Kind-Switch Encoder

The Kind() switch pattern used inside encoding/json-style libraries to walk arbitrary values.

go
func encode(v reflect.Value) string {    switch v.Kind() {    case reflect.Ptr, reflect.Interface:        if v.IsNil() {            return "null"        }        return encode(v.Elem())    case reflect.Struct:        parts := make([]string, 0, v.NumField())        t := v.Type()        for i := 0; i < v.NumField(); i++ {            if !t.Field(i).IsExported() { // reflect can see unexported fields but can't Set/Interface() them                continue            }            parts = append(parts, fmt.Sprintf("%q:%s", t.Field(i).Name, encode(v.Field(i))))        }        return "{" + strings.Join(parts, ",") + "}"    case reflect.Slice, reflect.Array:        parts := make([]string, v.Len())        for i := range parts {            parts[i] = encode(v.Index(i))        }        return "[" + strings.Join(parts, ",") + "]"    case reflect.String:        return fmt.Sprintf("%q", v.String())    default:        return fmt.Sprintf("%v", v.Interface())    }}

reflect.StructOf & DeepEqual

StructOf builds an entirely new struct type at runtime (used by some ORMs/GraphQL libraries); DeepEqual is the recursive comparison reflection powers under the hood.

go
dynType := reflect.StructOf([]reflect.StructField{    {Name: "Name", Type: reflect.TypeOf(""), Tag: `json:"name"`},    {Name: "Score", Type: reflect.TypeOf(0.0), Tag: `json:"score"`},})instance := reflect.New(dynType).Elem()instance.FieldByName("Name").SetString("dynamic")fmt.Println(instance.Interface()) // {dynamic 0}// reflect.DeepEqual recursively compares Kind-appropriate fields --// this is what testify/require.Equal and cmp.Diff build on top of.a := map[string]int{"x": 1}b := map[string]int{"x": 1}fmt.Println(reflect.DeepEqual(a, b)) // true, even though maps aren't == comparable

Reflection Gotchas

Runtime panics and subtle mistakes unique to reflect-heavy code.

  • Unexported field access- Field()/FieldByName() can read unexported fields, but .Interface() and .Set() on them panic with 'reflect: reflect.Value.Interface: cannot return value obtained from unexported field'
  • CanAddr() vs CanSet()- a Value can be addressable but still not settable if it came from an unexported field or a non-pointer receiver
  • reflect.ValueOf(x).Elem() on non-pointer- panics with 'call of reflect.Value.Elem on <kind> Value' unless x is a Ptr or Interface
  • Comparing reflect.Type with ==- safe and fast (types are interned/comparable), unlike comparing arbitrary reflect.Value
  • Nil interface vs nil pointer wrapped in interface- v.IsNil() is required to detect the latter; a plain `== nil` check on the interface is famously wrong
  • Cost of repeated TypeOf/ValueOf- each call walks runtime type metadata; cache reflect.Type lookups keyed by go type in hot encoders
Pro Tip

Reach for reflection only at the edges of your program (encoders, ORMs, dependency injection, generic-ish utilities before generics existed) — it bypasses compile-time type checking and is noticeably slower than direct code, so keep it out of hot paths and prefer Go generics where they now suffice.

Was this cheat sheet helpful?

Explore Topics

#GoReflection#GoReflectionCheatSheet#Programming#Advanced#TypeAndValue#InspectingStructFields#Mutating#Values#CheatSheet#SkillVeris

Frequently Asked Questions

21 categories · pick one to explore

Does SkillVeris have a tech blog, and what does it cover?
Yes, the SkillVeris blog has over 500 articles covering AI and machine learning, programming, web development, DevOps, cloud, security, databases and career guidance. Articles are practical and answer-first, and many use the Learn Through Hobbies approach, teaching technical concepts through cricket, music, gaming or cooking analogies. Everything is free to read.
What is the SkillVeris tech glossary and how big is it?
The SkillVeris glossary is a free reference of roughly 2,000-plus technology terms, each with a clear plain-language definition. It spans AI, programming, web, DevOps, cloud, security and database vocabulary, so whenever a lesson, article or job description uses jargon you do not recognise, the glossary gives you a fast, reliable answer.
Are the developer cheat sheets on SkillVeris free to download?
The cheat sheets are completely free to use, like everything else on SkillVeris. Each sheet condenses a language or tool into its essential syntax, commands and patterns for quick reference while coding. They are designed for rapid lookup during real work, complementing the deeper explanations found in study notes and courses.
Which programming references and cheat sheets are available?
Cheat sheets cover the platform's main domains, including programming languages, AI and ML tooling, web development, DevOps, cloud, security and databases, matching the topics of the 37 live courses. Each sheet lists related reading links and hashtags, so you can jump from a quick reference into fuller study notes or blog articles.
How do I find the meaning of a technical term quickly?
Search the SkillVeris glossary, which holds around 2,000-plus terms with concise, plain-language definitions. Each entry gets to the point in its first sentence, then links to related reading like blog posts or study notes for deeper context. It is faster and more consistent than sifting through scattered search results.
Is the SkillVeris blog good for beginners learning to code?
Yes, many blog articles are written specifically for beginners, and the Learn Through Hobbies style makes them unusually approachable: you might learn Python concepts through cricket or understand APIs through cooking. With 500-plus articles across skill levels, beginners can start with fundamentals and keep reading as they advance, entirely free.
Can cheat sheets replace full courses for learning a language?
No, cheat sheets are references, not teaching tools; they assume you already understand the concepts and just need syntax or commands fast. To actually learn a language, take a structured SkillVeris course with its 24–40 lessons and assessments, then keep the cheat sheet beside you while practising in Code Lab.
How often are new blog articles published on SkillVeris?
The blog grows regularly and already exceeds 500 articles, with new posts added as courses launch and technologies evolve. Topics track the platform's catalogue across AI, programming, web development, DevOps, cloud and security, so checking the Blog section periodically surfaces fresh tutorials, explainers and career-focused pieces, all free to read.
Does the glossary cover AI and machine learning terms?
Yes, AI and machine learning vocabulary is a major part of the roughly 2,000-plus term glossary, covering everything from foundational terms to modern concepts around LLMs, RAG and MLOps. Definitions are plain-language and answer-first, which helps when dense AI papers or course lessons throw unfamiliar jargon at you.
Are there cheat sheets for interview preparation?
Cheat sheets work well as interview-day refreshers because they compress syntax, commands and key concepts into scannable references. For dedicated preparation, combine them with the SkillVeris interview questions feature, which includes readiness scoring, plus study notes for depth. Reviewing a relevant cheat sheet just before an interview steadies recall under pressure.
Can I read the tech blog without signing up?
Yes, the blog is freely readable, and SkillVeris never charges for content. All 500-plus articles are open, covering tutorials, concept explainers and career advice. Creating a free account adds value elsewhere on the platform, like course progress tracking and certificates, but reading the blog requires no commitment at all.
How is the SkillVeris glossary different from Wikipedia?
The glossary is purpose-built for learners: definitions are short, plain-language and answer-first, sized for a quick lookup mid-lesson rather than a deep encyclopedic read. Entries also cross-link to related SkillVeris study notes, blog posts and courses, so a definition becomes a doorway into structured learning instead of a dead end.
Do blog articles use the Learn Through Hobbies method?
Many blog articles teach technical topics through hobby analogies, a hallmark of the SkillVeris blog, so you will find articles explaining programming through cricket, machine learning through music, or system design through cooking. The analogy is the teaching device; the article still delivers the real technical concept underneath.
Where can I find quick programming references while coding?
Open the SkillVeris cheat sheets, which are built exactly for that moment: compact, scannable references for syntax, commands and common patterns across languages and tools. Keep the relevant sheet in a browser tab while you work in Code Lab or your own editor, and dip into the glossary for terminology.
Is there a glossary entry for terms I meet in job descriptions?
Very likely yes, with roughly 2,000-plus terms across AI, programming, web, DevOps, cloud, security and databases, the glossary covers most jargon that appears in tech job descriptions. Decoding a listing this way helps you judge role fit honestly and prepares you to discuss those terms in interviews.
Are the blog articles written for the Indian tech audience?
The blog serves Indian learners plus a worldwide audience. Content stays globally relevant while acknowledging realities that matter in India, such as free access being essential for students and freshers, and career guidance that connects naturally to the SkillVeris jobs portal, which aggregates roles across India, UK, USA, Germany and Remote.
Can I suggest a topic for the blog or glossary?
SkillVeris content grows in response to what learners need, so feedback is welcome through the platform's support channels. If a term is missing from the glossary or a topic deserves an article, telling the team helps prioritise it. Meanwhile, the AI Mentor can answer the question immediately, 24/7, at any depth.
Do cheat sheets and glossary entries link to deeper learning?
Yes, every cheat sheet and glossary entry carries related reading links into study notes, blog articles and courses, plus concept hashtags for discovering similar content. This cross-linking means a thirty-second lookup can smoothly become a structured learning session whenever you decide you want more than a quick answer.
What makes SkillVeris programming references trustworthy?
The references are written to strict internal quality standards, kept consistent with the platform's 37 live courses, and never padded with invented statistics or hype. Definitions and cheat sheets are reviewed against the same content contracts that govern courses, and the answer-first style makes any inaccuracy easy to spot and correct.
How do the blog, glossary and cheat sheets fit into my learning routine?
Use them as satellites around your main course: read blog articles for context and motivation, hit the glossary the instant jargon appears, and keep cheat sheets open while coding. Together with study notes, Code Lab and the 24/7 AI Mentor, they turn passive reading into a complete, free learning system.

What Learners Say

Real journeys from the SkillVeris community — swipe for more.

SkillVeris taught me Python through Cricket. Now I’m building real projects and feeling confident!
Arjun S. · B.Tech Student
The best platform for hobby-based learning. Concepts finally stick.
Priya R. · Data Analyst
I went from zero coding to a portfolio of projects — all by learning through my love for gaming. Landed my first internship!
Kabir M. · CS Undergraduate
Trending Topics50 popular tags — tap to explore
Trending CoursesAll 37 free courses — tap to browse