perf: split delAllArgs into delAllArgs and delAllArgsStable #1945
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 original
delAllArgs
method is stable but requires more copying operations to maintain the order of elements.delAllArgs
method todelAllArgsStable
to maintain stable behavior.delAllArgs
method for non-stable functionality, improving runtime efficiency.Depending on the specific use case:
delAllArgsStable
when stability (order preservation) is required.delAllArgs
when stability is not necessary.In the case of handling headers in
h.h
, the order of headers is not important. Refer to net/http header.go, where the Del function calls textproto.MIMEHeader.Del. This function is implemented using a map, and the map delete operation is inherently unstable.Benchmark compare
delAllArgsStable
anddelAllArgs
Benchmark result: