Skip to content

Adding documentation to clarify the result of DispatchTime(uptimeNanoseconds: 0) #210

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
merged 3 commits into from
Feb 10, 2017
Merged

Adding documentation to clarify the result of DispatchTime(uptimeNanoseconds: 0) #210

merged 3 commits into from
Feb 10, 2017

Conversation

ktopley-apple
Copy link
Contributor

The documentation does not make it clear that DispatchTime(uptimeNanoseconds: 0) produces a value that represents the current nanoseconds since boot, not the time of boot. The fix adds a documentation comment to that effect.

(Radar 28814085)

Resolves SR-2807.

@ktopley-apple
Copy link
Contributor Author

@swift-ci please smoke test

@moiseev
Copy link
Contributor

moiseev commented Feb 8, 2017

Shouldn't it be added here as well?

@ktopley-apple
Copy link
Contributor Author

ktopley-apple commented Feb 8, 2017 via email

@ktopley-apple ktopley-apple changed the title Dispatch time 0 doc Adding documentation to clarify the result of DispatchTime(uptimeNanoseconds: 0) Feb 9, 2017
@moiseev moiseev merged commit 787dd92 into swiftlang:master Feb 10, 2017
@ktopley-apple ktopley-apple deleted the dispatch-time-0-doc branch February 10, 2017 20:32
@das
Copy link
Contributor

das commented Feb 16, 2017

please don't merge PRs with merge commits, branches should be rebased and flattened before merging them to trunk for a clean history.

das pushed a commit that referenced this pull request Feb 21, 2017
Adding documentation to clarify the result of DispatchTime(uptimeNanoseconds: 0)

Signed-off-by: Daniel A. Steffen <dsteffen@apple.com>
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