-
Notifications
You must be signed in to change notification settings - Fork 132
fn: fix loop var capture and clarify naming in ParSliceErrCollect
#1772
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
Conversation
Pull Request Test Coverage Report for Build 17325825267Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good, but worth checking on the underlying behaviour of ParSliceErrCollect per my comment/question.
da6a600
to
4452a12
Compare
Ensure each goroutine captures its own index/value in ParSliceErrCollect, and rename variables for clearer intent. Avoids closure capture bug and makes concurrency guards explicit. Add explicit context cancellation handling so the function returns a partial error map along with a non-nil error when the caller's context is canceled or times out.
4452a12
to
f0ea040
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Ensure each goroutine captures its own index/value in
ParSliceErrCollect
, and rename variables for clearer intent. Avoids closure capture bug and makes concurrency guards explicit.