typedef in C: Type Aliases, Readability, and Why the Linux Kernel Uses It Sparingly

typedef does not create a new type. It creates an alias for an existing type. typedef int Integer; means Integer and int are the same type, interchangeable everywhere. The compiler does not distinguish them. There is no type safety gained. What you gain is readability: a name that communicates intent rather than mechanical detail.

#Basic Syntax and Common Patterns#link

byte communicates that this variable holds a raw byte, not a character or a small integer. user_id_t communicates domain meaning. The _t suffix is a POSIX convention for typedef names. You will see it everywhere in system headers: size_t, pid_t, time_t. The compare_fn alias hides the grotesque syntax of a function pointer declaration behind a readable name.

#typedef with structs: Eliminating the struct Keyword#link

In C, declaring a struct variable requires the struct keyword every time: struct Point p; typedef lets you drop it. This is idiomatic in most C codebases, though the Linux kernel famously avoids it for structs, preferring the explicit struct keyword as a signal that you are dealing with a composite type.

#The Debate: To typedef or Not#link

The argument against typedef for structs: it hides the fact that you are working with a struct, making it harder to grep for struct definitions and obscuring the type category. The argument for: it reduces noise, especially with nested structs and function pointers. In application code, typedef is standard. In kernel and systems code, you will see both styles. Read the project's existing code and match its convention.

typedef is a readability tool. It does not add safety. It does not prevent misuse. It makes declarations shorter and intent clearer. Use it for function pointer types, for domain-specific integer aliases, and for structs in application code. Next: enum, which gives names to integer constants and creates a poor man's algebraic type.