In object-oriented and functional programming, an immutable object is an object whose state cannot be modified after it is created. This is in contrast to a mutable object, which can be modified after it is created. In some cases, an object is considered immutable even if some internally used attributes change but the object's state appears to be unchanging from an external point of view. For example, an object that uses memoization to cache the results of expensive computations could still be considered an immutable object.
Immutable objects are often useful because they are inherently thread-safe. Other benefits are that they are simpler to understand and reason about and offer higher security than mutable objects.
Read more about Immutable Object: Background, Implementation, Copy-on-write, Usage
Famous quotes containing the words immutable and/or object:
“Of course politics is an interesting and engrossing thing. It offers no immutable laws, nearly always prevaricates, but as far as blather and sharpening the mind go, it provides inexhaustible material.”
—Anton Pavlovich Chekhov (1860–1904)
“Is not prayer also a study of truth,—a sally of the soul into the unfound infinite? No man ever prayed heartily, without learning something. But when a faithful thinker, resolute to detach every object from personal relations, and see it in the light of thought, shall, at the same time, kindle science with the fire of the holiest affections, then will God go forth anew into creation.”
—Ralph Waldo Emerson (1803–1882)