On 10/21/2015 07:24 PM, Andrei Alexandrescu wrote:
On 10/21/2015 11:08 AM, Timon Gehr wrote:
Exactly. There would be no mutable aliasing. This way, the persistent
data type can behave like a mutable value type, such as a COW or eager
copy variant, but with nicer/different performance characteristics. It
would be great if exchanging different implementation strategies for
value semantics will be as seamless as possible. (If the initially
chosen strategy turns out to be wrong, this makes the fix easy.) Of
course, the implementation of the persistent data structure will be in
terms of non-mutating and possibly O(1)-COW operations only.
Makes sense. Now that we got to talk - did you submit the bugs you found
with DIP25? -- Andrei
Yup:
https://issues.dlang.org/buglist.cgi?email1=timon&emailreporter1=1&emailtype1=substring&list_id=204001&query_format=advanced&resolution=---&short_desc=DIP25&short_desc_type=allwordssubstr
