You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because one uses .load_int here but not ~load_int, this method returns not bool but slice (self) with remaining contract data and only then the bool flag.
In practice this method is useless for now (nobody calls it) and as I understood, there is no ability (flag) to disable it in compilation, so it just takes space in compiled code cell. Is this a feature or not?
Can we add such flag?
The text was updated successfully, but these errors were encountered:
In practice this method is useless for now (nobody calls it) and as I understood, there is no ability (flag) to disable it in compilation, so it just takes space in compiled code cell. Is this a feature or not? Can we add such flag?
When one compile any tact smart-contract, it generates
lazy_deployment_completed
method for him .But, the purpose of this method seems unclear for me:
documentation says that:
But in practice, this method returns not
bool
but(slice,bool)
.Is this a bug or a feature? (probably a bug due to the poor implementation in FUNC, but if a feature, one should document it more clearly):
Because one uses
.load_int
here but not~load_int
, this method returns not bool butslice
(self) with remaining contract data and only then the bool flag.In practice this method is useless for now (nobody calls it) and as I understood, there is no ability (flag) to disable it in compilation, so it just takes space in compiled code cell. Is this a feature or not?
Can we add such flag?
The text was updated successfully, but these errors were encountered: