fix the `job_preemption_points` name clash
Rename the type-class parameter to `job_preemptive_points` to avoid a name clash with the the definition of the same name. Keep `JobPreemptionPoints` to match `TaskPreemptionPoints`. This does not result in a name clash.
Showing
- analysis/facts/preemption/job/limited.v 31 additions, 35 deletionsanalysis/facts/preemption/job/limited.v
- analysis/facts/preemption/rtc_threshold/limited.v 2 additions, 2 deletionsanalysis/facts/preemption/rtc_threshold/limited.v
- analysis/facts/preemption/task/floating.v 6 additions, 6 deletionsanalysis/facts/preemption/task/floating.v
- analysis/facts/preemption/task/limited.v 4 additions, 4 deletionsanalysis/facts/preemption/task/limited.v
- model/preemption/limited_preemptive.v 14 additions, 10 deletionsmodel/preemption/limited_preemptive.v
- model/task/preemption/limited_preemptive.v 2 additions, 2 deletionsmodel/task/preemption/limited_preemptive.v
Loading
Please register or sign in to comment