Make if/else :? return the entire stack, allow blocks as conditions#160
Merged
nick-paul merged 2 commits intoaya-lang:masterfrom Nov 19, 2025
Merged
Conversation
…lse_return_multiple # Conflicts: # test/colon_ops.aya
Collaborator
|
Thanks, this change makes sense to me! I wasn't thinking about it when I added it originally |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I was caught by surprise by if/else twice:
true)I changed both of these things.
Allowing blocks seems useful to me. It's an adjacent idea to #149
Returning multiple values is what I intuitively expected.
Though it may break existing code if it relies on the stack being cleared.