Quick study sessions to strengthen memory and retain key concepts.
Design choice: When to use wrappers?
Use wrappers for nullability, collections, and APIs. Wrappers are useful when null values are necessary, such as in…
View Card →Object methods: What do wrappers offer?
Wrappers provide methods for conversion, parsing, and more. Wrapper classes include methods for tasks like parsing strings to…
View Card →Unboxing pitfalls: What can go wrong?
Unboxing null values causes NullPointerExceptions. Unboxing converts a wrapper to a primitive. If the wrapper is null, a…
View Card →Performance tradeoffs: When is primitive better?
Use primitives for performance-critical tasks. Primitives avoid the overhead of object creation and are more memory-efficient. In performance-critical…
View Card →Autoboxing: What is it?
Autoboxing is the automatic conversion between primitives and wrapper objects. Java automatically converts primitives to their corresponding wrapper…
View Card →Identity vs. Value: How do they differ?
Primitives compare by value, wrappers can compare by identity. Primitives use '==' for value comparison. Wrappers also support…
View Card →Autoboxing pitfalls: What should you watch out for?
Autoboxing can cause unexpected performance issues and NullPointerExceptions. Autoboxing is automatic conversion between primitives and wrappers. It adds…
View Card →Nullability: Why use wrapper types?
Wrappers can represent non-existent values with null. In Java, primitive types can't be null, making them unsuitable for…
View Card →Primitive vs. Wrapper: Why does it matter?
Wrappers offer nullability and object methods, but are less performant. Primitive types, like 'int', are more efficient in…
View Card →Why is `==` risky when comparing two `Integer` objects?
`==` compares object references, not reliable numeric equality. Wrapper objects can look like primitives while still following object…
View Card →