-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
register_as_coercion fails when no coercion map was already discovered #29517
Comments
Branch: u/caruso/register_coercion |
Changed branch from u/caruso/register_coercion to none |
Commit: |
Branch: u/caruso/register_coercion |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
Doctest failure here:
I cannot remember if this behavior was intentional or not as we might not wanted to create a coercion after explicitly checking that there was not one as a safety check. However, even if that was the case, I think this is the more natural thing to permit since the user should really know what they are doing to add this. So once the doctest is fixed, then you can set a positive review on my behalf. |
Reviewer: Travis Scrimshaw |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
Missing author name. |
Author: Xavier Caruso |
Changed branch from u/caruso/register_coercion to |
Compare:
with:
CC: @tscrim
Component: coercion
Author: Xavier Caruso
Branch/Commit:
1b1467b
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/29517
The text was updated successfully, but these errors were encountered: