What do Generics allow programmers to avoid?

What do Generics allow programmers to avoid?

• A. Rigid, hard-coded type definitions — one class/method works for many types
• B. Runtime type checks
• C. Memory leaks
• D. Null checks

Answer: (A)

Generics let you write code that can work with any type while staying type-safe. By introducing a type parameter and using that parameter in a class or method, you write one implementation that can handle int, string, or any custom type without duplicating code for each type. The compiler ensures that only values of the chosen type are used, catching type errors early and avoiding the need to create separate, hard-coded versions for every type. This flexibility is the core benefit—reusing the same logic across many types while preserving strong typing. Generics aren’t primarily about memory leaks or null checks, and while they can reduce the need for explicit casts, their main purpose is to avoid rigid, single-type definitions by enabling a single, reusable implementation.

Generics let you write code that can work with any type while staying type-safe. By introducing a type parameter and using that parameter in a class or method, you write one implementation that can handle int, string, or any custom type without duplicating code for each type. The compiler ensures that only values of the chosen type are used, catching type errors early and avoiding the need to create separate, hard-coded versions for every type. This flexibility is the core benefit—reusing the same logic across many types while preserving strong typing. Generics aren’t primarily about memory leaks or null checks, and while they can reduce the need for explicit casts, their main purpose is to avoid rigid, single-type definitions by enabling a single, reusable implementation.