Avoid crash when running task with (*task).run == nil #31
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.
The following program currently leads to a crash due to nil pointer
dereference:
Fix this by checking (*task).run before running it. This way we keep the
semantics of returning a result for every submitted task. The
alternative solution would be to not enqueue the task on
(*WorkerPool).Submit("foobar", nil) and return either nil or an error.
Both would lead to an imbalance between bumber of submitted tasks and
returned results.