Opened 18 months ago

Last modified 5 weeks ago

#31746 new enhancement

Move __pow__ directly on CategoryObject

Reported by: Vincent Delecroix Owned by:
Priority: major Milestone: sage-9.8
Component: misc Keywords:
Cc: Michael Jung, Travis Scrimshaw Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: #31721 Stopgaps:

Status badges

Description (last modified by Vincent Delecroix)

In #31721 a generic __pow__ has been introduced on Parent. It might be more natural to have this operation directly on CategoryObject. However

  • do we have objects inheriting from CategoryObject but not from Parent/Element and would benefit from this __pow__?
  • check that it does not hurt performance of Element.__pow__.

Change History (7)

comment:1 Changed 18 months ago by Vincent Delecroix

Dependencies: #31721

comment:2 Changed 17 months ago by Travis Scrimshaw

IMO, it is always best to put things in as general of a place as possible. Even if there is not a use-case currently, that doesn't mean there won't be one in the future. The bigger thing is the performance of Element subclasses.

comment:3 Changed 17 months ago by Vincent Delecroix

Description: modified (diff)

comment:4 Changed 14 months ago by Matthias Köppe

Milestone: sage-9.4sage-9.5

comment:5 Changed 10 months ago by Matthias Köppe

Milestone: sage-9.5sage-9.6

comment:6 Changed 6 months ago by Matthias Köppe

Milestone: sage-9.6sage-9.7

comment:7 Changed 5 weeks ago by Matthias Köppe

Milestone: sage-9.7sage-9.8
Note: See TracTickets for help on using tickets.