Le 10/10/2012 15:53, Simon King a écrit :
Why not "RecursiveSet"? The word "Generated" seems redundant to me.
And what you tell about the role of "post_process" makes me think it could be
renamed into "branch_cut".
Best regards,
Simon
Hello,
The post_process hardly depend on a fonction (placed in itertools of
sage) which is "imap_and_filter_none". There are two points on this
output processing : you cut branches and you also apply an output
fonction...
I like the Set suffix for the name. As the feature returns a parent with
category, it seems fine for me the name should be close to blablablaSet.
IMHO, the feature accept multiples roots but no one would search for
"forest", we naturally search for Tree, TreeLikeStruture, ...
In an other directions, we should make a micro patch to modify the
documentation of EnumeratedSet, FiniteEnumeratedSet, ...Set to advertise
the user of the existance of the searchForest (old name) feature. I
don't know if sphnix accept such references... Just putting in other doc
: for set defined with roots and a children fonction,
see:..../SearchForest. Perhaps also, the code should be moved out from
bactrack.py...
Cheers,
Nicolas B.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
