Skip to content
This repository has been archived by the owner on Oct 16, 2024. It is now read-only.

Reduce overhead of modifying a value with Collections #169

Open
2 of 6 tasks
alicederyn opened this issue Jun 8, 2016 · 0 comments
Open
2 of 6 tasks

Reduce overhead of modifying a value with Collections #169

alicederyn opened this issue Jun 8, 2016 · 0 comments

Comments

@alicederyn
Copy link
Collaborator

alicederyn commented Jun 8, 2016

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
@alicederyn alicederyn changed the title Reduce memory overhead of modifying a value Reduce memory overhead of modifying a value with Collections Jun 8, 2016
@alicederyn alicederyn changed the title Reduce memory overhead of modifying a value with Collections Reduce overhead of modifying a value with Collections Jun 8, 2016
This was referenced Oct 5, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant