On 2013-02-10, Nils Bruin <nbr...@sfu.ca> wrote: > The following came up on #14084 but it relates much more to the kinds > of things happening on #13370. > > Since parents are unique in sage, so if you ask for a parent to be > constructed, you really don't know what you get back. It might be a > freshly produced one, it might be one that is currently also > referenced by other active data structures, or it might be a > dereferenced copy that the garbage collector didn't get to yet. > > To preserve programmer and user sanity in such an environment one has > to be very careful with what happens to parents: they have to be > immutable. In practice one cannot insist on literal immutability (as > in: no bits in the memory block allocated for the parent are allowed > to change, nor in any blocks pointed to) for efficiency reasons.
I'd like to propose to add to Sage the following frameworks, to deal with the related issues: adoption, custody, child welfare monitoring. They together with the coersion can form Sage law enforcement Super-framework, which should also include war on bugs framework (currently known as patchbot)... Dima (runs away :)) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
