Added lock to protect the RNG. #54
Merged
Conversation
This file contains hidden or 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
Contributor
|
+1 |
2 similar comments
Contributor
|
+1 |
Contributor
|
+1 |
dustinhiatt-wf
added a commit
that referenced
this pull request
Feb 9, 2015
Added lock to protect the RNG.
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.
CODE REVIEW
Apparently, the RNG is not threadsafe. Need to protect that in the package. Allocating a new generator at every run proved to be more costly than protecting with lock.
@tannermiller-wf @alexandercampbell-wf @beaulyddon-wf @rosshendrickson-wf @ericolson-wf @stevenosborne-wf @tylertreat-wf