Simplify and optimize RemoveMagicPrefixLine. #36
Merged
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.
This PR implements a suggestion from https://github.com/andygrunwald/go-gerrit/pull/10/files#r116843309.
If body has
")]}'\n"
prefix, there's no need to usebytes.IndexByte
to find the first'\n'
character, it's known to be at index 4 becausebytes.HasPrefix(body, []byte(")]}'\n"))
was true.Since this is called often, it's probably a good idea to factor out
[]byte(")]}'\n")
into a package scope variable, instead of potentially allocating once perRemoveMagicPrefixLine
call.