On 2013-10-10 02:22, Sean Kelly wrote:

Only that this would have to be communicated to the user, since moving data 
later is problematic. Today, I think it's common to construct an object as 
unshared and then cast it.

What is the reason to not create it as "shared" in the first place?

--
/Jacob Carlborg

Reply via email to