Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use global variables for contract state not only for Tact's utility variables #797

Open
anton-trunov opened this issue Sep 7, 2024 · 1 comment
Open

Use global variables for contract state not only for Tact's utility variables #797

anton-trunov opened this issue Sep 7, 2024 · 1 comment
Labels
scope: codegen Code generation, a.k.a. compiler backend

Comments

@anton-trunov
Copy link
Member

No description provided.

@anton-trunov anton-trunov added the scope: codegen Code generation, a.k.a. compiler backend label Sep 7, 2024
@Gusarich
Copy link
Member

in many cases with small smart contracts it can be more optimal to keep all state variables on stack instead of using global variables

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
scope: codegen Code generation, a.k.a. compiler backend
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@anton-trunov @Gusarich