Home Dashboard Directory Help
Search

Complex.Asin and Complex.Acos in System.Numerics yields incorrect results by leppie


Status: 

Closed
 as Deferred Help for as Deferred


2
0
Sign in
to vote
Type: Bug
ID: 790328
Opened: 6/17/2013 12:28:34 PM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description

When the result of either of these are complex (imag != 0) and

Complex.Asin is broken where imaginary part is zero and real part is negative.
Complex.Asin is broken where imaginary part is positive.

Complex.Acos is broken where imaginary part is zero and real part is positive.
Complex.Acos is broken where imaginary part is negative.
Details
Sign in to post a comment.
Posted by Microsoft on 7/16/2013 at 9:29 AM
Hi leppie

Thank you for your feedback.

We are not going to be able to address this issue in our next release due to other priorities, however we have logged it and we will continue thinking about addressing it in a future release.

Regards,
Alex Ghiondea
.NET Framework team
Posted by Microsoft on 6/17/2013 at 7:30 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 6/17/2013 at 12:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by leppie on 6/17/2013 at 9:31 PM
The correct way to handle this is as follows:

https://ironscheme.codeplex.com/SourceControl/changeset/101144#IronScheme/Microsoft.Scripting/Math/Complex64.cs

Also make sure negative 0.0 does not popup, else the results will be incorrect to.