Add EventLoop.now API for getting the current time #3015
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Code that tries to work with
NIODeadline
can be challenging to test usingEmbeddedEventLoop
andNIOAsyncTestingEventLoop
because they have their own, fake clock.These testing event loops do implement
scheduleTask(in:_)
to submit work in the future, relative to the event loop clock, but there is no way to get the event loop's current notion of "now", as aNIODeadline
, and users sometimes find thatNIODeadline.now
, which returns the time of the real clock, to be surprising.Modifications
Add
EventLoop.now
to get the current time of the event loop clock.Result
New APIs to support writing code that's easier to test.