-
Notifications
You must be signed in to change notification settings - Fork 4
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
The spec. #2
The spec. #2
Conversation
|
||
The function _next_ performs the smallest possible step of computation, mapping the input _State_ into an output _State_, **or failing** (all of the situations in which it fails will be described later). | ||
|
||
The function _isTerminal_ determines if a given _State_ is terminal, meaning that if _isTerminal(s) == true_, where _s_ is of type _State_, then _next(s)_ must either fail or return _s_ unchanged. |
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.
next(s) must either fail or return s unchanged.
is an "unchanged s" really possible? if next is supposed to "perform the smallest possible step of computation", then state must have changed, hence same state can not be returned.
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.
I guess it depends on whether you consider doing nothing, or no-op to be "a step of computation".
But the point I was trying to get across is that you define a terminal state by either saying "a terminal state is one from which no further computation can be done", or "a terminal state is a fixpoint with respect to the state-transition function".
And actually, I think I will have to commit to one of these in future, as my implementation efforts continue.
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.
- checked readme
- verified that machine.template.sol matches definitions
- ran type checks, received 7 warnings
reviewed court and Oracle, had the following issues understanding them:
|
Thank you @johannbarbie. These issues will be addressed along with the explanatory gif: #3 (comment). I will consider this issue closed. |
Resolves issue #1