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.
I converted the
Hints
to be pointers becausegocritic
(hugeParam
) reports that the hints are 80 bytes and heavy to copy.When using pointers instead we become sensitive to
nil
data and since theHints
holds pointers toHintSets
we needed to add checks to ensure no values were actually leftnil
. I started to wonder how much this would cost compared to just copying the hints and wrote some benchmarks. These are the results:Hints
is pointerHints
is copiedGiven this the code is much simpler and less fragile when not using pointers.