Fix a name clash

Two different things were named job_preemption_points in model/preemption/parameter.v and model/preemption/limited_preemptive.v (apparently, this was already known but never properly fixed). I offer to rename the instance that has the least occurences.

mentioned in merge request !205 (merged)

Thanks, Pierre!

Sergey, could you please take a look at this? I don’t recall what the original intention was. Why did we end up with this name clash?

CC: @sbozhko

I'll merge this soon-ish after the arrival-model cleanup has gone it. One question: I'm not 100% sure about the naming, @mmaida @sbozhko what do you think? Any ideas?

Feel free to pick any better name, I kinda chose the current name just based on filenames.

added 18 commits

• 4f003575...903e5476 - 16 commits from branch master
• 8d5d07d8 - Fix a name clash
• 6790f17f - squash! rename type class and parameter

Compare with previous version

marked this merge request as draft from 6790f17f

added 2 commits

• fe929dfe - explain choice of name in a comment
• fddc0c28 - squash! fix and tweak comments

Compare with previous version

added 1 commit

• f925eeee - fix the `job_preemption_points` name clash

Compare with previous version

marked this merge request as ready

resolved all threads

enabled an automatic merge when the pipeline for f925eeee succeeds

merged