Hi Paul, On 2014-05-28, Paul-Olivier Dehaye <paul-olivier.deh...@math.uzh.ch> wrote: > Christian's point is key. The absolute hardest problem to solve is where to > anchor semantic information so that others can contribute to it easily, > ... > Right now, by lack of a better place, it is put in sage.
I think you miss the point of what Nathann and I try to say. I think Nathann agrees that it is a reasonable idea to have a @combinatorial_map decorator in front of a method (I do agree), provided that it gives useful information to some people (this is the case now), and provided that it does not have a negative impact for people who don't use this information---and currently it *does* have a negative impact, because of a slow-down in potentially time-critical methods. Last attempt before leaving office: - Currently we have a lose-lose situation: When people put @combinatorial_map, then it has a negative impact to some other people (the slow-down), and it is difficult to use the added information for those who want to do proper queries. - We should better have a win-win situation: When people put @combinatorial_map, then it should not change the method (to not slow-down stuff), and the added information should be accessible to queries in a reasonable way. Cheers, Simon -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/d/optout.
