-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Hermes event queue and Hermes reactor #135
Conversation
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.
LGTM. I'm just not sure about if are we going to include some mechanism for initialializing each runtime extension in this PR as mentioned by Steven?
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.
See comments and change requested PR here:
#173
* fix(hermes): changes requested for event queue * fix(hermes): Reintroduce mechanism to advise runtime extensions of a new context * fix(hermes): fix code format
Yes we did in the latest changes. |
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.
Thanks, this will help in getting our APIs 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.
LGTM
Description
HermesEventQueue
implementation as a mpsc FIFO queue. This struct is s singleton object which is stores as a staticOnceCell
variable.HermesReactor
struct, which should a general manager which orchestrates all hermes execution like: running and stepping runtime extensions; initialising and holding an event queue instance and manages event loop thread.Related Issue(s)
#125