-
Notifications
You must be signed in to change notification settings - Fork 210
Support MethodCall in if/else branches #1177
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
base: master
Are you sure you want to change the base?
Conversation
update from main
update from master
update from main
|
@Turupawn getting the CI linting to pass can be a little tricky. To locally run what the CI runs, do |
|
Can you add a test file to crates/codegen/tests/fixtures that demonstrates the code that now passes but before didn't? |
|
@micahscopes Thank you for the heads up, I ran the formatter this time. @cburgdorf I added a demo that shows what works now. However I also discovered this issue #1185 that is currently happening in the main branch. Even though the issue is related, imo it should be treated separately. |
| let v1 := v0 | ||
| let v2 := 0 | ||
| if gt(x, 10) { | ||
| v2 := get_value1(v1) |
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.
It looks like the name of the functions being called get_value1 does not match the actual name of the function teststruct_get_value1
Update from main
…mir-testground
MethodCallis now supported in if/else branches as returned valeslower_and_format_callfunction to encapsulate repeated code