-
Notifications
You must be signed in to change notification settings - Fork 12
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
Keep track of input actions in the environment #42
Conversation
Currently, the only action type that is an input action is a physical action. Later we will add enclave and federate connections.
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 good to me
const bool fast_fwd_execution_{default_fast_fwd_execution}; | ||
|
||
std::set<Reactor*> top_level_reactors_{}; | ||
/// Set of actions that act as an input to the reactor program in this environment |
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.
Is this the set of physical actions then ?
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.
At the moment yes, but it will include enclave (and federated) connections soon.
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!
This change allows actions to be owned by the environment. It further adds the concept of 'input actions' which are actions that act as an input to the reactor program. Currently, this is limited to physical actions. Later, enclave and federate connections will be added. Since this mechanism allows us to infer if
keepalive
is needed or not, therun_forever
parameter of the Environment is dropped.