-
Notifications
You must be signed in to change notification settings - Fork 3
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
Implement Multi-Threading into the Codebase #58
Conversation
…eading-infrastructure
…threads and pools with return types.
… now only for internal use as a utility to the main thread.
…ized example file.
…eading-infrastructure
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.
Overall looks good. Please look at the comments and modify or justify the method/reason for doing it the way implemented.
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.
All comments resolved, and requested changes have been made.
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.
Making the one change requested in the devcontainer.json file and then it looks like it will be ready for merging.
Elegant Example Running
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.
Looks great! Thanks for your patience.
…ructure Implement Multi-Threading into the Codebase
This PR implements an interface class that aims to give programmers the ability to easily multi-thread their code without worrying about low-level thread and memory management. Just inherit the base class and implement a couple pure virtual functions.
Since resource access management (resource locking) for the users implemented code can not be controlled internally by the interface, users should know when and how to acquire locks with mutexes and they should also use atomic whenever possible. A guide detailing this will be implemented shortly.
Closes issue #29