When does a short string avoid the heap and when do views expire?

A strong answer

A strong candidate frames When does a short string avoid the heap and when do views expire? around the exact memory layout, compiler semantics, and hardware execution model covered in string: Characters, Storage and Small-String Optimization. Cover size, capacity, null guarantee, small-string storage, and why views must refresh after growth.

Your first 0_Language/implementation/string.cpp version duplicated the whole class and left the moved-from object holding nullptr, which made c_str return null and operator== crash inside strcmp. The cleaned second version below keeps one class, guards null input and leaves a moved-from object in a valid empty state:

std::string is that design completed, with capacity management, SSO and full value semantics. Learn the repaired ownership model here and the standard behavior becomes predictable.

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: Explain size, capacity and null terminator guarantees for std::string.
• Mastery of core invariant: Predict when short strings avoid heap allocation through SSO.
• Mastery of core invariant: Use reserve, c_str, at and operator+= without invalidating views.
• 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.