Maybe something changed in the standard library's handling of floats? Max?
> On Feb 20, 2017, at 13:26, Philippe Hausler wrote:
>
> That would be new; I have not seen that failure before. the method is quite
> droll - it just calls sin/cos and resets the m values accordingly.
>
> Did sin/cos
That would be new; I have not seen that failure before. the method is quite
droll - it just calls sin/cos and resets the m values accordingly.
Did sin/cos change? the values being sent in are reasonable (not at a point it
would be in any question of the return value)
> On Feb 20, 2017, at 9:1
Foundation folks, have you seen this before?
TestFoundation/TestNSAffineTransform.swift:187: error:
TestNSAffineTransform.test_Rotation_Radians : XCTAssertEqualWithAccuracy
failed: ("10.0") is not equal to ("-10.0") +/- ("0.001") - y (expected: -10.0,
was: 10.0):
Jordan
> On Feb 20, 2017, at
