-
Notifications
You must be signed in to change notification settings - Fork 39
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
Make reactions.go
and other similar methods interrupt action block execution
#82
Comments
@nikvoloshin I'm not sure it should be implemented this way. Go-like functions are dialogue-related and shouldn't declare the way user should write their action's code. Moreover, there could be some cases when the user could place |
@morfeusys Thanks for your feedback! |
For now, the user must ensure by himself that there is no code after
reactions.go
, otherwise, this code will be executed, moreover, it will be executed beforetoState
action block. Although it breaksreactions.go
semantic and documentation that states the following: "Changes the state of scenario and executes it's action block immediately".For example, such a code:
will produce the output:
Shouldn't get to this
.I think, that it's not the desired behaviour and we should think about, for example, making
reactions.go
and other go-like methods returnkotlin.Nothing
. It will make user and compiler sure, that current action block execution interrupts afterreactions.go
The text was updated successfully, but these errors were encountered: