-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
<complex>: pow(complex<float>, int) returns complex<float> instead of complex<double> #325
Comments
Neargye
added a commit
to neargye-forks/STL
that referenced
this issue
Dec 11, 2019
It's reproduced only when the Line 1588 in 3b0a1c9
|
Try to fix during #383 |
Neargye
added a commit
to neargye-forks/STL
that referenced
this issue
Dec 12, 2019
Neargye
added a commit
to neargye-forks/STL
that referenced
this issue
Dec 15, 2019
Neargye
added a commit
to neargye-forks/STL
that referenced
this issue
Dec 16, 2019
Neargye
added a commit
to neargye-forks/STL
that referenced
this issue
Dec 16, 2019
Neargye
added a commit
to neargye-forks/STL
that referenced
this issue
Jan 22, 2020
StephanTLavavej
pushed a commit
that referenced
this issue
Jan 24, 2020
StephanTLavavej
added
fixed
Something works now, yay!
and removed
work in progress
labels
Jan 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Standard states that
pow(complex<float>, int)
should treat both arguments ascomplex<double>
, indicating that it should also returncomplex<double>
. Instead it returns acomplex<float>
.WG21-N4835 [cmplx.over]/3 states:
libc++ will return the correct type. libstdc++ will not. https://godbolt.org/z/_TscRV
Also tracked by Microsoft-internal VSO-177118.
The text was updated successfully, but these errors were encountered: