Rename from immutable to persistent
See original GitHub issueThere is some immediate backlash about immutable collections by Java users, as their understanding of the concept is either getting a full copy per operation, or receiving an exception on mutating methods.
The persistent
keyword along with some references to Big O perf in the documentation may help spread the understanding of the difference.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:13 (1 by maintainers)
Top Results From Across the Web
Java: File#reName() successfully rename the file, but the file ...
So to refresh the file reference, I need to File file = new File("test1.txt") again? · 1. You should not specify the type...
Read more >Copy, rename, and move objects | Cloud Storage
Rename an object · In the Google Cloud console, go to the Cloud Storage Buckets page. · In the list of buckets, click...
Read more >Unable to rename network devices named em(1,2,3) in yast ... - SUSE
Changing device names or Network interface cards in Yast, or by modifying /etc/udev/rules.d/70-persistent-net.rules does not take effect. Networking is fine and ...
Read more >Why rename things? - Nature
Names can be descriptive, but where possible they too should be immutable for distinction and retrieval purposes.
Read more >How to Use the zoneadm Command to Rename a Zone
Document number: E37628-04 Copyright © 2004, 2015, Oracle and/or its affiliates. All rights reserved.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In the Java world, “Persistent” has always meant “stored in a database”. It’s the “P” in “JPA”, which is why I steered away from it. Either way, whatever words you use for immutable/persistent collections should be less typing than the name for Mutable ones (and Unmodifiable ones) in order to steer lazy programmers toward doing the safest thing.
I like this idea, but it looks like implementations of the
ImmutableCollection
interface don’t have to be persistent. That being said, perhaps the concrete implementations should contain the wordPersistent
.