Worker API Finalization#5
Merged
Merged
Conversation
Owner
Author
Comment about latest changesImagine main thread as the manager. It owns all resources of the game. Worker threads are basically workers. They're stateless. All they need is their scratchpad and data that they work on. No game worker should have access to the game state. They're simple workers and when I created ThreadExecutionContext, I forgot that I need to make them different from the main thread. That's all. |
…e inline helpers to ThreadContext.h
Owner
Author
|
Workers finalized in the way I'd like them to be for now. I'll open another PR later to implement async stuff, so the rest of things are going to be finished in the future in appropriate time |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.