We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the current interface to the MPC library, you cannot add the symbolic i and MPC complex numbers:
i
sage: from sage.rings.complex_mpc import MPComplexField sage: MPC = MPComplexField() sage: MPC(1) + SR(i) Traceback (most recent call last) ... TypeError: unsupported operand parent(s) for '+': 'Complex Field with 53 bits of precision' and 'Symbolic Ring' sage: SR(i) + MPC(1) Traceback (most recent call last) ... TypeError: unsupported operand parent(s) for '+': 'Symbolic Ring' and 'Complex Field with 53 bits of precision'
This works with "usual" complex numbers:
sage: CC(1) + SR(i) 1.00000000000000 + 1.00000000000000*I
and with the "number-field" version of i (now the default after #18036):
sage: MPC(1) + i 1.00000000000000 + 1.00000000000000*I
CC: @nexttime @slel
Component: coercion
Keywords: mpc complex numbers multiprecision.org
Issue created by migration from https://trac.sagemath.org/ticket/11808
The text was updated successfully, but these errors were encountered:
Updating ticket description after #18036 was merged in 9.3.beta2.
This, which was failing in the original report, now works:
but this still fails:
sage: MPC(1) + SR(i)
Sorry, something went wrong.
robertwb
No branches or pull requests
With the current interface to the MPC library, you cannot add the symbolic
i
and MPC complex numbers:This works with "usual" complex numbers:
and with the "number-field" version of
i
(now the default after #18036):
CC: @nexttime @slel
Component: coercion
Keywords: mpc complex numbers multiprecision.org
Issue created by migration from https://trac.sagemath.org/ticket/11808
The text was updated successfully, but these errors were encountered: