What is an opaque pointer and why use it?

A strong answer

A strong candidate frames What is an opaque pointer and why use it? around the exact memory layout, compiler semantics, and hardware execution model covered in Opaque Pointers and API Encapsulation. Explain how opaque pointers hide implementation details, reduce recompilation, and enforce encapsulation across translation units.

Exposing struct member layouts inside public header files causes two critical architectural failures: broken encapsulation and ABI brittleness.

1. State Tampering: Client code can bypass API validation functions and mutate internal fields directly (conn.is_authenticated = 1;), breaking library invariants.
2. ABI Fragility: Suppose version 1.1 of the library inserts an SSL context pointer before timeout_ms:

   struct DbConnection {
       int socket_fd;
       char host[64];
       void *ssl_ctx; /* Added in v1.1 */
       int timeout_ms;
       int is_authenticated;
   };

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: Expose incomplete struct types in public header interfaces to enforce encapsulation.
• Mastery of core invariant: Confine complete struct definitions to implementation translation units.
• Mastery of core invariant: Preserve Application Binary Interface (ABI) compatibility across library updates.
• 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.