{"push_id":1149990591,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"fd136cc28cb64109e534cfc5206be8a9c9adc258","before":"4fbed473e26f8511c1396d2441b11666d73c8deb","commits":[{"sha":"956b6b1cad1932daef3dc27c50cff119fd859b83","author":{"name":"Nicola Salmoria","email":"5e507b2faec7cda54f739fe5cd7de7c6248e2b51@gmail.com"},"message":"SR-1417: Add non-optional overloads of XCTAssertEqual and XCTAssertNotEqual\n\nPreviously, the only version of the functions that accepted values was the one that implicitly wraps them into Optionals. This generated a confusing error message when the assert failed. Having a separate overload that accepts non-optional types ensures that the correct description is printed when the assert fails.","distinct":true,"url":"https://api.github.com/repos/apple/swift/commits/956b6b1cad1932daef3dc27c50cff119fd859b83"},{"sha":"1b7a4479556100e892dc688d6a3fa4f0616c6d9a","author":{"name":"Brian Croom","email":"fe7eaaa8ba12b78764d3dddda72dc977cd74d565@gmail.com"},"message":"Test the failure messages for optional and non-optional XCTAssertEqual variants","distinct":true,"url":"https://api.github.com/repos/apple/swift/commits/1b7a4479556100e892dc688d6a3fa4f0616c6d9a"},{"sha":"fd136cc28cb64109e534cfc5206be8a9c9adc258","author":{"name":"Brian Gesiak","email":"0c09f9ac95ab928573a6428d24847856289273b0@gmail.com"},"message":"Merge pull request #2788 from briancroom/pr-2551\n\nSR-1417: Add non-optional overloads of XCTAssertEqual and XCTAssertNotEqual","distinct":true,"url":"https://api.github.com/repos/apple/swift/commits/fd136cc28cb64109e534cfc5206be8a9c9adc258"}]}
{"actor":{"display_login":"modocache"}}