Enable query engine update from collider #137
Merged
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
utilForever
added a commit
to utilForever/CubbyFlow-v1
that referenced
this pull request
Dec 21, 2017
utilForever
added a commit
to utilForever/CubbyFlow-v1
that referenced
this pull request
Dec 21, 2017
utilForever
added a commit
to utilForever/CubbyFlow-v1
that referenced
this pull request
Dec 21, 2017
utilForever
added a commit
to utilForever/CubbyFlow-v1
that referenced
this pull request
Dec 21, 2017
utilForever
added a commit
to utilForever/CubbyFlow-v1
that referenced
this pull request
Dec 21, 2017
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.
Without this feature, making any spatial query from "set" type surfaces from parallel execution context will cause race condition. This is originally reported by https://github.com/utilForever/CubbyFlow/issues/217. Introducing mutex could be a natural solution, but that requires heavy assumption on the parallel executer (which is currently std::thread at the moment) which is not ideal -- it can be OpenMP, TBB, PPL, pthread, etc. In the near future, however, thread-safety-ness should be well documented for the public APIs.