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

go: write a more efficient replacement for strings.Split #124

Open
saser opened this issue Dec 8, 2020 · 0 comments
Open

go: write a more efficient replacement for strings.Split #124

saser opened this issue Dec 8, 2020 · 0 comments

Comments

@saser
Copy link
Owner

saser commented Dec 8, 2020

In many of my solutions, I use strings.Split to iterate over my input. That sometimes causes many allocations, increasing the memory footprint and runtime for my solutions. Sometimes I do not need to hold the entire list of splits in memory; simply iterating over them would be enough. For these situations, I should try to use a more efficient way of iterating over the input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant