Isolate handling of temporal context and metronome #7
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.
Some of the more intricate pieces of
ClockQuantizer
were pulled out and wrapped in aTemporalContextDriver
shim that abstracts the following items:ISystemClockTemporalContext
, if one is providedClockAdjusted
andMetronomeTicked
eventsISystemClockTemporalContext
or if a providedISystemClockTemporalContext
does not provide a metronome.TemporalContextDriver
provides the "internal" metronome, timer resources are freed up while in quiescent state.TemporalContextDriver
is taken out of quiescing stateIAsyncDisposable
support ofSystem.Threading.Timer
between TFMsIn order to clean things up a bit more,
bool ISystemClockTemporalContext.ProvidesMetronome
was changed toTimeSpan? ISystemClockTemporalContext.MetronomeIntervalTimeSpan
. This allows implementers to not only specify the fact that an external metronome is being provided, but also its interval time-span.