The "no gc" crowd

[Sean Kelly]

On Oct 9, 2013, at 9:42 AM, Jacob Carlborg <doob at me.com> wrote:
> 
>> On 2013-10-09 17:48, Sean Kelly wrote:
>> 
>> Okay so following that… it might be reasonable if the location of data keyed off the attribute set at construction.  So "new shared(X)" puts it in the shared pool.
> 
> I thought that was obvious. Is there a problem with that approach?

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.