Skip to content

Fix Swift dispatch time comparisons #182

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

Closed
wants to merge 2 commits into from

Conversation

lilyball
Copy link

This PR does two things:

  1. It makes < comparisons on DispatchWallTime not crash.
  2. It makes < comparisons against DispatchTime.distantFuture and DispatchWallTime.distantFuture behave as expected.

This is a port of swiftlang/swift#5078, but without the tests because I don't see any Swift tests in this repo.

@das das assigned mwwa and unassigned das Oct 4, 2016
@das
Copy link
Contributor

das commented Oct 4, 2016

@mwwa please also review swiftlang/swift#5078 (which I cannot assign to you for some reason)

@das
Copy link
Contributor

das commented Oct 4, 2016

once done, we should probably also clone this for the swift-3 branch (in both repos)

@lilyball
Copy link
Author

The other PR has now been merged. This one still needs to be reviewed.

@mwwa
Copy link
Contributor

mwwa commented Oct 17, 2016

@swift-ci please test

@lilyball
Copy link
Author

This was merged into apple/swift many months ago. Is the failed test here the only thing holding this up? The details link is a 404 so I can't see what went wrong.

@CodaFi
Copy link
Contributor

CodaFi commented May 30, 2017

The details link is a 404 so I can't see what went wrong.

Let's at least fix that much

@swift-ci please test

@lilyball
Copy link
Author

lilyball commented Jun 1, 2017

Looks like it passed this time.

@CodaFi
Copy link
Contributor

CodaFi commented Jun 1, 2017

Looks like this change was made during an overlay sync up. Thanks for the original!

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