Join GitHub today
me.pool.pull stucks in a loop #443
ok sorry i did not know that :)
but to be honest, and if I can give my opinion, I believe that keeping track of all child references to ensure no sub or sub or sub sub (and so on) child refers to any parent references, is maybe a bit complexifying the deepcopy for nothing. And this kind of reference cycle issue (leading to a stack overflow) is somehow something usual for a developer and more a matter of being careful than something else (in my opinion). Not to mention that in both case it will throw an exception (either the browser or then the deepcopy function)
So, here's where things get very problematic. A cycle may be created and totally contained in the object itself, without referring to its own parent. In this case, it is safe to deepcopy with cycle protection.
On the other hand, any object in the pool that references a live object could be a problem in user code. However a deepcopy with cycle protection is still safe here.
Third, deepcopy is only used in the constructor (