Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why are single-argument arithmetic functions in the coercion model? #597

Closed
robertwb opened this issue Sep 6, 2007 · 2 comments
Closed

Why are single-argument arithmetic functions in the coercion model? #597

robertwb opened this issue Sep 6, 2007 · 2 comments
Labels
c: basic arithmetic r: duplicate t: bug

Comments

@robertwb
Copy link
Contributor

robertwb commented Sep 6, 2007

Is there any advantage to having _neg_c/neg/_neg_c_imple as opposed to overriding neg?

Component: basic arithmetic

Issue created by migration from https://trac.sagemath.org/ticket/597
@sagetrac-mabshoff sagetrac-mabshoff mannequin added this to the sage-2.10 milestone Sep 11, 2007
@sagetrac-mabshoff sagetrac-mabshoff mannequin modified the milestones: sage-2.10, sage-2.9 Nov 3, 2007
@robertwb
Copy link
Contributor Author

comment:3

Now that cpdef methods are used, one can just implement __neg__ and __inverse__, we don't need this infrastructure for unary operations (and it slows them down).

We should do a full search of the source.

@mwhansen
Copy link
Contributor

comment:4

This is a now duplicate of #2072, which is more recent.

@mwhansen mwhansen removed this from the sage-3.2.1 milestone Nov 14, 2008
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: basic arithmetic r: duplicate t: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mwhansen @robertwb