-
Notifications
You must be signed in to change notification settings - Fork 22
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
fix(engine) Avoid wrapping return in a tuple. #1056
Conversation
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.
Ah, that makes sense, thanks, looks great!
The test failure looks suspicious though, do you have an idea why we have this change @maximebuyse? |
I just pushed a fix. It was just a dumb mistake. Tests are passing now. |
@W95Psp I fixed the issue with the typing of |
Fantastic! |
Nothing changed in the generation of PV, but the verification doesn't work any longer. |
@jschneider-bensch may want to look at why PV verification fails |
Fixes #1044.
This fixes phase
LocalMutation
that was wrappingreturn
expressions inside a tuple (to pass a state) but the state is lost in case of areturn
so we should not try to pass the state (otherwise it is not caught byDropReturnBreakContinue
).