You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2024. It is now read-only.
Currently, if Guava is present, Builder.from(value) makes a mutable copy of every collection in value, and .build() then creates immutable copies of them all. If the collection isn't changed, there is no need for a mutable copy, and the two values should share the immutable instances.
This issue does not cover behaviour when Guava is not available.
Collection types affected:
List
Set
Map
Multiset
ListMultimap
SetMultimap
The text was updated successfully, but these errors were encountered:
alicederyn
changed the title
Reduce memory overhead of modifying a value
Reduce memory overhead of modifying a value with Collections
Jun 8, 2016
alicederyn
changed the title
Reduce memory overhead of modifying a value with Collections
Reduce overhead of modifying a value with Collections
Jun 8, 2016
Currently, if Guava is present,
Builder.from(value)
makes a mutable copy of every collection invalue
, and.build()
then creates immutable copies of them all. If the collection isn't changed, there is no need for a mutable copy, and the two values should share the immutable instances.This issue does not cover behaviour when Guava is not available.
Collection types affected:
The text was updated successfully, but these errors were encountered: