Skip to content

[gardening] Remove XCTAssertNotNil calls where parameter is a non-optional type #1516

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

Merged

Conversation

otaviolima
Copy link
Contributor

No description provided.

@otaviolima otaviolima changed the title Remove XCTAssertNotNil calls where parameter is a non-optional type [gardening] Remove XCTAssertNotNil calls where parameter is a non-optional type Apr 15, 2018
@parkera
Copy link
Contributor

parkera commented Apr 15, 2018

@swift-ci please test

@parkera
Copy link
Contributor

parkera commented Apr 15, 2018

What happened here in the first place? Did we change the results from nullable to non-null?

@otaviolima
Copy link
Contributor Author

What happened here in the first place? Did we change the results from nullable to non-null?

I did not check the code changes over time, but I have a feeling that is related to the annotations on the Darwin counter-part being updated which then make those init swing from nullable to non-nullable annotation. But that is just an assumption with no fact check what so ever. :)

@ianpartridge
Copy link
Contributor

@swift-ci please test and merge

@swift-ci swift-ci merged commit 57e5f7f into swiftlang:master Apr 16, 2018
@otaviolima otaviolima deleted the remove-superfluous-XCTAssertNotNil branch April 16, 2018 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants