#8746: Equality of posets element is very slow
----------------------------------+-----------------------------------------
   Reporter:  hivert              |       Owner:                            
       Type:  defect              |      Status:  positive_review           
   Priority:  blocker             |   Milestone:  sage-4.4                  
  Component:  combinatorics       |    Keywords:  Comparison posets elements
     Author:  Florent Hivert      |    Upstream:  N/A                       
   Reviewer:  Andrey Novoseltsev  |      Merged:                            
Work_issues:                      |  
----------------------------------+-----------------------------------------

Comment(by hivert):

 I've sent the following message to sage-release and sage-devel but it
 doesn't seems to pass through
 {{{
 > This release candidate for Sage 4.4 closed 19 tickets (on top of
 > 4.4.alpha1). On trac, these tickets were labeled as "merged into
 > 4.4.alpha2", but then I decided that alpha2 should be the same as rc0.

 Cool ! So there is a good chance that we'll have 4.4 for sage 20.5 next
 week
 at Toronto ! This is perfect...

 I'm however embarrassed to have the following question/request:
  - how do we decide to make some ticket blocker for a release. Is it
 possible
 at this stage to make #8746 blocker for 4.4. Here is the rationale:

 The Posets library (by Franco Saliola) allows to deals with small
 Partially
 Ordered SETS. This kind of structure is extremely useful an common in
 combinatorics. Usually we play with one poset at a time, seeking for
 particular property of one of them. For my research I had to play with
 many of
 them and I discovered that the equality was (very fast) but completely
 broken,
 preventing them to be used eg. as key in dict. This was fixed in #7438. We
 solved this together with Nicolas Borie (which is a student of Nicolas
 ThiƩry)
 and this was merged in alpha0. However we didn't realize that doing this
 we
 slowed of the most common usage that is comparing element in a single
 poset by
 several order of magnitude. I take the full blame for this mistake which I
 consider as an important regression. #8746 solve this common use issue.

 So is there still possible to merge #8746 while having 4.4 out before sage
 days 20.5 ? I realize that I should have marked this ticket as critical or
 blocker at its creation but I don't know how this is decided so that I
 never
 change this field... Many Apologies for this late request.
 }}}

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8746#comment:5>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to