On Thursday, February 7, 2013 2:19:51 PM UTC+1, Simon King wrote: > > Hi, > > On 2013-02-06, Nils Bruin <[email protected] <javascript:>> wrote: > > On Feb 6, 12:05 pm, Simon King <[email protected]> wrote: > >> There is the idea to always keep the last N created parents alive by a > >> strong reference. Couldn't this easily be done, by appending "self" to > a > >> list (and removing the first entry, when the list is too long), while > > > > Yes, except you want to do it circularly: > > OK, that's what Robert did anyway, in #14073. He states there: "I don't > think this code should go in unless it's clearly shown to be a problem." > I guess that's a good idea. First wait if there is really a problem to > fix. > > We could also include the code but somehow disabled, or commented out, so that one who really wants it could easily enable it.
> In any case, I think it should be clearly documented that, for good > performance, one should avoid cross-parent arithmetic operations > altogether, or one should at least keep a pointer to the parent of the > result. > > But where should I put such a warning? I don't think > sage.structure.coerce would be a good location, because only experts > would look there. So, it should be a (thematic) tutorial. What would you > suggest? Speaking of tutorials, I should finally try to convert my > coercion > worksheet into a tutorial... > I would suggest to duplicate the info :) Of course that's twice as much work. > > Best regards, > Simon > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
