Opened 8 years ago

Last modified 7 years ago

#16427 new enhancement

Explain the rationale for having both categories and a hierarchy of Cython abstract classes for Parents and Elements

Reported by: nthiery Owned by:
Priority: major Milestone: sage-6.4
Component: categories Keywords:
Cc: sage-combinat, hivert, SimonKing, darij, nbruin, pbruin, vbraun, tscrim, ohanar Merged in:
Authors: Nicolas M. Thiéry Reviewers:
Report Upstream: N/A Work issues:
Branch: u/nthiery/explain_the_rationale_for_having_both_categories_and_a_hierarchy_of_cython_abstract_classes_for_parents_and_elements (Commits, GitHub, GitLab) Commit: 01fdfabeeee07c6157df72b409303c0adce67174
Dependencies: Stopgaps:

Status badges

Description

The title says it all :-)

Upcoming here: benchmarks to support and illustrate the discussion.

One of the threads that triggered this ticket:

​https://groups.google.com/d/msg/sage-devel/tVrqhKQ1QDs/lnru7s0feKkJ

Change History (6)

comment:1 Changed 8 years ago by tscrim

  • Cc tscrim added

comment:2 Changed 8 years ago by nthiery

  • Branch set to u/nthiery/explain_the_rationale_for_having_both_categories_and_a_hierarchy_of_cython_abstract_classes_for_parents_and_elements

comment:3 Changed 8 years ago by ohanar

  • Cc ohanar added
  • Commit set to 01fdfabeeee07c6157df72b409303c0adce67174

New commits:

​322b69516427: Explain the rationale for having both categories and a hierarchy of Cython abstract classes for Parents and Elements
​01fdfab16427: Typo fix

comment:4 Changed 8 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:5 Changed 7 years ago by jdemeyer

Should this be set to needs_review?

comment:6 Changed 7 years ago by SimonKing

Again: Should this be set to needs_review, Nicolas?

Note: See TracTickets for help on using tickets.