New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize string building for NamespacedName #95821
Optimize string building for NamespacedName #95821
Conversation
Hi @markusthoemmes. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @liggitt |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, markusthoemmes The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/priority backlog |
/test pull-kubernetes-bazel-test |
/triage accepted |
What type of PR is this?
What this PR does / why we need it:
This applies a microoptimization to the
String()
function oftypes.NamespacedName
. It's something we carry around downstream and I don't quite see a reason not to upstream it.Based on this benchmark
The results are
Which is almost too good to be true 馃槀. Maybe I'm missing something obvious here.
Does this PR introduce a user-facing change?: