Closed turion closed 11 months ago
An implementation of waitClock
that schedules deterministically in ScheduleT
is not so trivial. Possibly, we have to add another constructor to ScheduleT
for measuring time.
The Periodic
clocks are already implemented with ScheduleT
, so this is solved by reimplementing FixedStep
in terms of Periodic
. Still, Millisecond
mustn't be broken by that.
Invalid since https://github.com/turion/rhine/pull/171
Right now we only have a deterministic schedule for two (atomic)
FixedStep
clocks clocks, i.e. not even for sequentially or parallelly composed ones. This suggests to letFixedStep
have side effects inScheduleT Int
and take the schedule from there. This would mean changing the definitions ofMillisecond
possibly.