Test scheduler does absolute time #63
Open
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.
There are several operators which take a
Timeargument and act at a point in time. This PR introduce the somewhat hackyTestTimewhich===Timeand can therefore be used to signify an absolute point in "testing time". This means we can write marble-style virtual time tests for these operators and need not resort to async tests. For example:This unearthed a bug where the
alias_methoddirective (now removed) inVirtualTimeSchedulermeant that invokation ofschedule_at_absolute_with_statewould bypass theTestSchedulerand invokeVirtualTimeScheduler. Rather than try to correct this, the PR cleans up the naming of scheduler methods so as to make the alias unnecessary.