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.
props.isHeavy()
logic within the_gr_
functions as they are no longer called unless alreadyCN_GR_[0-5]
IS_CN_HEAVY_XHV
to match existingIS_CN_HEAVY_TUBE
and use it everywhere the long-form test was usedIS_HEAVY
toIS_CN_HEAVY
to better match theIS_CN_HEAVY_(TUBE|XHV)
IS_CN_HEAVY
the same everywhereprops.isHeavy()
was called separatelyIS_CN_HEAVY
is also defined everywhereCN_STEP4
macro was used, as itsprops.isHeavy()
was changedcn_vaes_enabled
tests for slightly improved readability, and allows to not validate the other bools unless VAES is available (now in roughly likelihood-to-be-false and importance order)Tested compile, and valid accepts for
cn-heavy/xhv
andghostrider
but I do not have any VAES capable rigs, so it still needs a diligence proof test on something that does have it. Also don't have any pools to test thecn-heavy/0
orcn-heavy/tube
but I think thecn-heavy/xhv
test proves those by association.Should be a tiny bit nicer since all these are validated once into constexpr-bool's the same way everywhere.