rec: check bounds of rcode stats counter index (safe right now) #15139
+6
−4
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.
Safe right now as
LWResult::d_rcode
gets assigned from the 4 bitrcode
in the header. But that might change one day. I'd rather makeLWResult::d_rcode
anuint8_t
, but that causes a conflict with the OOB resolving code that does not make a difference betweenres
andd_rcode
.Also fix a typo in a constant name and reorder fields in
LWResult
largest to smallest.Short description
Checklist
I have: