-
-
Notifications
You must be signed in to change notification settings - Fork 480
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.
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
__floordiv__ should be part of coercion model #2034
Comments
This comment has been minimized.
This comment has been minimized.
Author: Jeroen Demeyer |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:16
According to the "principle of least surprise", supporting floordiv for finite fields looks suspicious
If this is just an alias of division, why do we need it? |
comment:17
Replying to @videlec:
That's outside the scope of this ticket. This ticket only implements coercion for |
Reviewer: Vincent Delecroix |
comment:18
All right. Hope this will be fixed with #15260. |
Changed branch from u/jdemeyer/__floordiv___should_be_part_of_coercion_model to |
Add
__floordiv__
to the coercion model forRingElement
and change__floordiv__
to_floordiv_
where applicable.This does not change any semantics of floor division, but it does fix floor division in a few cases where coercion is involved. It also fixes various segmentation faults like
Finally, we also implement
__itruediv__
, which was forgotten when adding__truediv__
.Component: coercion
Author: Jeroen Demeyer
Branch/Commit:
3e0e5b8
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/2034
The text was updated successfully, but these errors were encountered: