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

Clean up setup execution method #1013

Merged
merged 7 commits into from
Apr 28, 2020
Merged

Conversation

stakx
Copy link
Contributor

@stakx stakx commented Apr 28, 2020

(This was triggered by the addition of a missing call to invocation.Return() in order to terminate a void method Invocation.)

`Invocation` expects to be "terminated" by a call to any of its
`Return` methods, yet that currently never happens for `void` methods
that have a setup but no further behavior configured.

Add the missing call.

The necessary guard condition is more complex than it needs to be,
let's clean that up in the following commits.
Moving `raiseEventResponse` further up should be safe because the call
to `invocation.CallBase()` it now precedes can only happen for `void`
methods, and the fluent API doesn't actually permit simultaneous use
of `Raises` and `CallBase` for `void` methods.
This change shouldn't be noticeable since the fluent API already does
not allow a second `Callback` on `void` methods.
@stakx stakx merged commit dc75009 into devlooped:master Apr 28, 2020
@stakx stakx deleted the invocation-return branch April 28, 2020 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant