TRT
Sign in
easyFoundationsconcept

Why is a scoped enumeration safer than plain integers?

Explain named values over integers, scoped names, explicit casts, and switch coverage.

TRT practice prompt — not a verified question from a named employer.

The Runtime Theory Team2 min read
Learn it firstEnumerations: enum and enum className a small set of values with an enumeration, see that it is an integer underneath, and learn why enum class avoids name clashes and accidental conversions and how switch warnings keep your code up to date.

A strong answer

A strong candidate frames Why is a scoped enumeration safer than plain integers? around the exact memory layout, compiler semantics, and hardware execution model covered in Enumerations: enum and enum class. Explain named values over integers, scoped names, explicit casts, and switch coverage.

Programs are full of values that are one of a few choices: a direction, a color, a state, an error code. The quickest way to store them is as integers, and that is the problem. What does status = 2 mean? Nothing in the code says. Nothing stops status = 7, which is not a valid choice, or a typo that stores the wrong one. Named constants such as const int Red = 0; help the reader, but they have no type, so nothing stops you passing a direction where a color is expected.

What you want is a type with a small set of named values, so that the compiler can check them. That is an enumeration.

In a production interview, always connect the specification rule to its concrete runtime consequence: state what lives on the stack versus the heap or static storage segment, how the compiler or operating system validates alignments, lifetimes, and error codes, and what happens under adversarial or boundary inputs (such as zero-length buffers, integer overflow, concurrent mutation, or partial I/O). Backing your explanation with a small trace of register/memory state transitions immediately separates senior systems engineers from candidates who only memorized syntax.

What the interviewer is listening for

  • Mastery of core invariant: Declare and use a scoped enumeration and say what values it holds.
  • Mastery of core invariant: Explain what enum class forbids that a plain enum allows.
  • Mastery of core invariant: Convert between enumerators and integers explicitly and predict the result.
  • Hardware and ABI awareness: Explaining how sizes, alignments, calling conventions, or kernel boundaries behave on real 64-bit targets rather than relying on implementation-defined assumptions.
  • Defensive engineering: Naming the exact compiler flags (-Wall -Wextra -Werror), static analyzers, or runtime sanitizers (-fsanitize=address,undefined,thread) that verify correctness in CI.

Common mistakes

  • Explaining only surface syntax without tracing the underlying memory addresses, ownership lifetime, or kernel/user-space state transitions.
  • Assuming undefined behavior (such as signed overflow, uninitialized reads, strict-aliasing violations, or dangling pointers) will "just work" because it passed an unoptimized -O0 debug build.
  • Ignoring return codes, partial reads/writes, alignment padding, or cleanup paths when an allocation or syscall fails midway through a function.

This answer walks

Practice follow-ups

  1. 01Why should a switch over an enum avoid a default label?

More interviews in this topic

easy · languageWalk through the internal structure of a Go channel (`hchan`), explain the exact table of channel state behaviors (nil vs open vs closed for send, receive.easy · languageHow does Go's compiler decide whether a variable is allocated on the stack or the heap (Escape Analysis), why is returning a value `User` often faster than.easy · languageExplain how Go's Concurrent Tri-Color Mark-and-Sweep GC works—why doesn't Go use a compacting/generational GC like the JVM, how does the Hybrid Write Barrier.

Not started

Sign in to save your learning progress.

Sign in to save