⚡️Optimize the slice access in Golang #198
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roma-glushko
changed the title
|
This looks like a duplicate of #150 |
|
Thanks for submitting this @roma-glushko. As @karololszacki pointed out, we already have another PR with a similar change and some discussion, so I ill close this one out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Optimizing the slice access in the golang loop source code per this subreddit conversation:
https://www.reddit.com/r/golang/comments/1h150ho/go_is_slower_than_java_on_same_code/
Golang's compiler doesn't do much optimization around slice access which leads to awful benchmark results.