Timeline for Internal Mutation of Persistent Data Structures
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 22, 2012 at 17:12 | vote | accept | GregRos | ||
| Oct 7, 2012 at 7:32 | answer | added | Petr | timeline score: 2 | |
| Oct 6, 2012 at 19:55 | comment | added | dan_waterworth | It wouldn't be an immutable datastructure, but it would be a confluent persistent datastructure. | |
| Oct 6, 2012 at 19:34 | answer | added | ratchet freak | timeline score: 0 | |
| Oct 6, 2012 at 19:33 | answer | added | supercat | timeline score: 2 | |
| Oct 6, 2012 at 19:21 | comment | added | Oded | It depends on what guarantees you are making to the clients. If this were to run in a multi-threaded environment, I wouldn't dare call it immutable as it isn't and the assumptions associated with immutability would not hold. | |
| Oct 6, 2012 at 19:05 | history | asked | GregRos | CC BY-SA 3.0 |