Quick study sessions to strengthen memory and retain key concepts.
How can autoboxing lead to hidden bugs in loops?
Repeated autoboxing can cause performance issues and subtle bugs. In a loop, autoboxing creates many unnecessary objects, leading…
View Card →When might you prefer primitives over wrappers?
Prefer primitives when performance and memory efficiency are crucial. Primitives are more memory-efficient and faster because they don't…
View Card →What is unboxing in Java?
Unboxing converts wrapper types to primitives. Unboxing is the reverse of autoboxing and occurs when a wrapper class…
View Card →What are the risks of using '==' with wrapper objects?
'==' checks object identity, not equality. Using '==' with wrapper objects compares their references, not their values. This…
View Card →How can autoboxing impact performance?
Autoboxing can introduce overhead due to object creation. Autoboxing automatically converts primitives to their corresponding wrapper classes, which…
View Card →Why might nullability matter when choosing between primitives and wrappers?
Wrappers can be null, while primitives cannot. In Java, wrapper classes can represent a 'null' value, which is…
View Card →What are wrapper classes in Java?
Wrapper classes provide object representation for primitive types. Wrapper classes in Java allow primitive types (int, char, etc.)…
View Card →Value consistency: How do wrappers compare?
Use '.equals()' for consistent wrapper comparison. Wrappers require '.equals()' to compare values reliably, as '==' may give false…
View Card →Common mistake: Using '==' with wrappers?
'==' checks reference, not value in wrappers. Using '==' with wrappers checks if two references point to the…
View Card →Reading Java code: How to spot autoboxing?
Look for primitives being assigned to wrapper collections or method calls. Autoboxing occurs when a primitive is added…
View Card →