Continue swizzling fields after solve_order #244
Merged
Conversation
This file contains hidden or 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
The partsel swizzler would either solve all the ordered fields _or_ up to max_swizzle fields in a random order. Now ordered fields come first, then the remaining unordered fields. This means randomizations with ordered fields may have more solver calls. Fixes issue fvutils#242
Member
|
This, also, is a good improvement. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The partsel swizzler would either solve all the ordered fields or up to max_swizzle fields in a random order. Now ordered fields come first, then the remaining unordered fields.
This means randomizations with ordered fields may have more solver calls.
Fixes issue #242