i#6831 sched refactor, step 5: Split check for whether to switch inputs #7079
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Splits the mode-specific middle of next_record() into a new virtual method
process_next_record_candidate() which is implemented in the new subclasses
scheduler_{dynamic,fixed,replay}.cpp.
Issue: #6831
derekbruening
changed the title
…ch/; make functions pure-virtual and override in test classes
abhinav92003
approved these changes
Nov 13, 2024
…th pick_next_input_for_mode
derekbruening
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Splits the mode-specific middle of next_record() into a new virtual method check_for_input_switch() for identifying whether to trigger a switch and call pick_next_input_for_mode(). The new method is implemented in the new subclasses scheduler_{dynamic,fixed,replay}.cpp.
Issue: #6831