Boxing (computer programming): Difference between revisions

Content deleted Content added
Zachs18 (talk | contribs)
Clarify Rust's usage of boxing and heap allocation. Change the Box citation to the module std::boxed, as the type std::boxed::Box's documentation now just refers to that anyway. Clarify that Arc is not required to *send* a value to another thread, just to *share* it (Box can be sent to other threads if the boxed type can be).
Alternate name
 
Line 1:
{{Short description|Programming language concept}}
{{redirect|Object type|another use|Class (computer programming)|the universal type|any type}}
{{More citations needed|date=August 2009}}
In [[computer science]], '''boxing''' (a.k.a. wrapping) is the transformation of placing a primitive type within an [[Object (computer science)|object]] so that the value can be used as a [[reference type|reference]]. '''Unboxing''' is the reverse transformation of extracting the primitive value from its wrapper object. '''Autoboxing''' is the term for automatically applying boxing and/or unboxing transformations as needed.