Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeyToHash possibly letting key interfaces escape to heap #107

Closed
karlmcguire opened this issue Dec 2, 2019 · 2 comments
Closed

KeyToHash possibly letting key interfaces escape to heap #107

karlmcguire opened this issue Dec 2, 2019 · 2 comments
Labels
kind/bug Something is broken. priority/P1 Serious issue that requires eventual attention (can wait a bit) status/accepted We accept to work on it.

Comments

@karlmcguire
Copy link
Contributor

karlmcguire commented Dec 2, 2019

As brought up in the performance Gopher channel, since we're using interface{} for keys, this call to keyToHash is probably letting the interface escape to heap.

Solution: switch over to string or []byte for public API calls.

@martinmr
Copy link
Contributor

@karlmcguire should the change be for keys or keys and values?

@martinmr martinmr added kind/bug Something is broken. priority/P1 Serious issue that requires eventual attention (can wait a bit) labels Feb 21, 2020
@minhaj-shakeel
Copy link
Contributor

Github issues have been deprecated.
This issue has been moved to discuss. You can follow the conversation there and also subscribe to updates by changing your notification preferences.

drawing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something is broken. priority/P1 Serious issue that requires eventual attention (can wait a bit) status/accepted We accept to work on it.
Development

Successfully merging a pull request may close this issue.

4 participants