Interpreter: handle explicit return when method type is Nil #12179
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asterite
added
kind:bug
asterite
force-pushed
the
bug/interpreter-return-method-type-nil
branch
from
2bf98d7 to
5db3dcc
Compare
asterite
force-pushed
the
bug/interpreter-return-method-type-nil
branch
from
5db3dcc to
949d477
Compare
beta-ziliani
approved these changes
Jul 1, 2022
oprypin
approved these changes
Jul 3, 2022
straight-shoota
approved these changes
Jul 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #12178
A similar logic is done when an implicit value is returned from a method, it was just missing in the case of an explicit return.