Skip to content

fix: handle return statements in init function separately #794

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Merged
merged 4 commits into from
Sep 5, 2024
Merged

fix: handle return statements in init function separately #794

merged 4 commits into from
Sep 5, 2024

Conversation

Gusarich
Copy link
Member

@Gusarich Gusarich commented Sep 5, 2024

Issue

Closes #775.

Checklist

  • I have updated CHANGELOG.md
  • I have added tests to demonstrate the contribution is correctly implemented: this usually includes both positive and negative tests, showing the happy path(s) and featuring intentionally broken cases
  • I have run all the tests locally and no test failure was reported
  • I have run the linter, formatter and spellchecker
  • I did not do unrelated and/or undiscussed refactorings

@Gusarich Gusarich requested a review from a team as a code owner September 5, 2024 10:27
@Gusarich Gusarich added this to the v1.5.0 milestone Sep 5, 2024
@anton-trunov anton-trunov merged commit 1e71838 into tact-lang:main Sep 5, 2024
3 checks passed
# for free to join this conversation on GitHub. Already have an account? # to comment
Reviewers

@anton-trunov anton-trunov anton-trunov approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.5.0
Development

Successfully merging this pull request may close these issues.

return-statement in init() results in a FunC compilation error
2 participants
@Gusarich @anton-trunov