Open halmaia opened 4 months ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Tagging subscribers to this area: @dotnet/area-system-numerics
The .NET’s DegreesToRadians uses a special implementation ((degrees Pi) / 180.0) which result could deviate from the widespread 0.017453292519943295 degrees’ version (especially in the case of extremely small numbers). For example converting 1.2345678912345678e-40° to radians in Python™ returns 2.154727454144645e-42. In .NET the result is 2.1547274541446447E-42. The difference is not big at all but could break tests. Why did the .NET team choose this implementation?