Skip to content
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

Event Tree Chaining #151

Closed
rakhimov opened this issue Dec 29, 2016 · 0 comments
Closed

Event Tree Chaining #151

rakhimov opened this issue Dec 29, 2016 · 0 comments

Comments

@rakhimov
Copy link
Owner

No description provided.

@rakhimov rakhimov modified the milestone: v0.13.0 Apr 29, 2017
rakhimov added a commit that referenced this issue May 7, 2017
The whole Instruction lifetime management is refactored
due to Rule being as a named variable.
The Model is responsible for all instructions.
This is similar to how Expression is handled due to Parameter.

Issue #151
rakhimov added a commit that referenced this issue May 7, 2017
Rules are like variables referenced by their names
and can have cycles.
In this case, cycles in instructions are valid;
however, it is not decidable
whether these instructions would halt upon execution.
It is not expected these cycles be used in practice.

Issue #151
rakhimov added a commit that referenced this issue May 9, 2017
rakhimov added a commit that referenced this issue May 9, 2017
The initializer validates
that event-tree linking happens only with end-state sequences.

Issue #151
rakhimov added a commit that referenced this issue May 9, 2017
Cyclic linking of event trees is statically undecidable
even though it may be valid.
In practice, it is not expected that cyclic instructions be used.

Issue #151
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant