Java Autoboxing: Difference between revisions
Jump to navigation
Jump to search
m (Ovidiu moved page Java Autoboxing and Unboxing to Java Autoboxing) |
No edit summary |
||
| Line 10: | Line 10: | ||
Autoboxing comes with a performance cost. Boxed values are wrappers around primitive types, and are stored on the heap. Therefore, boxed values use more memory and requires additional memory lookups to fetch the wrapped primitive type. | Autoboxing comes with a performance cost. Boxed values are wrappers around primitive types, and are stored on the heap. Therefore, boxed values use more memory and requires additional memory lookups to fetch the wrapped primitive type. | ||
=Autoboxing and Streams API= | |||
The Streams API has specialized stream types and API calls for primitive types, to avoid unnecessary autoboxing. | |||
=TODO= | =TODO= | ||
* https://docs.oracle.com/javase/tutorial/java/data/autoboxing.html | * https://docs.oracle.com/javase/tutorial/java/data/autoboxing.html | ||
Revision as of 18:17, 28 March 2018
Internal
Overview
Java has a mechanism called boxing that converts primitive types (such as int) into their corresponding reference types (java.lang.Integer). The opposite operation, converting reference types into their corresponding primitive types is called unboxing.
Autoboxing is a mechanism that performs boxing and unboxing automatically.
Autoboxing comes with a performance cost. Boxed values are wrappers around primitive types, and are stored on the heap. Therefore, boxed values use more memory and requires additional memory lookups to fetch the wrapped primitive type.
Autoboxing and Streams API
The Streams API has specialized stream types and API calls for primitive types, to avoid unnecessary autoboxing.